search for: dash_o_option

Hi Dan, lld takes a -emit-yaml option, which emits the intermediate representation(atoms) in YAML form. By default output goes to stdout, the user can control it by using the -o option too. The way its handled is, similiar to this piece of pseudo-code if (dash_o_option) outputFile = dash_o_option->value() else outputFile = "-" When lld tries to mix things that go to stdout using llvm::outs() and -emit-yaml, it starts to get this error. If there is a restriction like this, possibly it has to be mentioned somewhere for usecases (or) raw_fd...

...ml option, which emits the intermediate >> representation(atoms) in YAML form. >> >> By default output goes to stdout, the user can control it by using the -o >> option too. >> >> The way its handled is, similiar to this piece of pseudo-code >> >> if (dash_o_option) >> outputFile = dash_o_option->value() >> else >> outputFile = "-" >> >> When lld tries to mix things that go to stdout using llvm::outs() and >> -emit-yaml, it starts to get this error. >> >> If there is a restriction like this...

..., > > lld takes a -emit-yaml option, which emits the intermediate > representation(atoms) in YAML form. > > By default output goes to stdout, the user can control it by using the -o > option too. > > The way its handled is, similiar to this piece of pseudo-code > > if (dash_o_option) > outputFile = dash_o_option->value() > else > outputFile = "-" > > When lld tries to mix things that go to stdout using llvm::outs() and > -emit-yaml, it starts to get this error. > > If there is a restriction like this, possibly it has to be mentioned...

...mediate >>> representation(atoms) in YAML form. >>> >>> By default output goes to stdout, the user can control it by using the -o >>> option too. >>> >>> The way its handled is, similiar to this piece of pseudo-code >>> >>> if (dash_o_option) >>> outputFile = dash_o_option->value() >>> else >>> outputFile = "-" >>> >>> When lld tries to mix things that go to stdout using llvm::outs() and >>> -emit-yaml, it starts to get this error. >>> >>> If...

The high-level answer is that library code shouldn't hardcode output paths, including "-" and including using llvm::outs(). Library code should (in general) instead accept an ostream in its API and write to wherever it is being asked to write. If this is followed, the only place in any program using llvm::outs() is code which is not part of a "library" -- i.e. it is the

...iate >>> representation(atoms) in YAML form. >>> >>> By default output goes to stdout, the user can control it by using the -o >>> option too. >>> >>> The way its handled is, similiar to this piece of pseudo-code >>> >>> if (dash_o_option) >>> outputFile = dash_o_option->value() >>> else >>> outputFile = "-" >>> >>> When lld tries to mix things that go to stdout using llvm::outs() and >>> -emit-yaml, it starts to get this error. >>> >>> If...

Hi, When I run the below example, it results in :- hello world LLVM ERROR: IO failure on output stream. Testcase :- #include <llvm/Support/raw_ostream.h> int fn() { std::string errorInfo; llvm::raw_fd_ostream out("-", errorInfo); out << "world\n"; return 0; } int main(int argc, char **argv) { llvm::outs() << "hello\n"; fn();

...t; > lld takes a -emit-yaml option, which emits the intermediate > representation(atoms) in YAML form. > > By default output goes to stdout, the user can control it by using the -o > option too. > > The way its handled is, similiar to this piece of pseudo-code > > if (dash_o_option) > outputFile = dash_o_option->value() > else > outputFile = "-" > > When lld tries to mix things that go to stdout using llvm::outs() and > -emit-yaml, it starts to get this error. > > If there is a restriction like this, possibly it has to be mentio...