search for: llvm_ostream

On 11/30/06, Andrew Lenharth <andrewl at lenharth.org> wrote: > The llvm_ostreams, which you take the address of go out of scope very > quickly, and are only stored by address in the bytecode writer, thus > the writers have a pointer to a stack allocated object they are to > write to. This crashes. The attached version leaks :-) It is a work around. If I understand c...

On 11/30/06, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > On 11/30/06, Andrew Lenharth <andrewl at lenharth.org> wrote: > > The llvm_ostreams, which you take the address of go out of scope very > > quickly, and are only stored by address in the bytecode writer, thus > > the writers have a pointer to a stack allocated object they are to > > write to. This crashes. > > The attached version leaks :-) > It is a w...

Actually, take a look at the current TOT for llvm-gcc4. Jim & I put a patch in there yesterday that should make things work with llvm_ostreams. -bw On 11/30/06, Bill Wendling <isanbard at gmail.com> wrote: > On 11/30/06, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > > On 11/30/06, Andrew Lenharth <andrewl at lenharth.org> wrote: > > > The llvm_ostreams, which you take the address of go ou...

The attached patch fixes a bootstrap failure introduced by the use of llvm_streams. Best Regards, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-gcc.patch Type: text/x-patch Size: 1217 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061130/d4b11c90/attachment.bin>

llvm-gcc is producing segmentation fault when running with -emit-llvm. Running cc1 in valgind produces the warning: ==12768== at 0x8D042C: llvm::llvm_ostream& llvm::llvm_ostream::operator<< <llvm::Module>(llvm::Module const&) (Streams.h:41) ==12768== by 0x8D0464: llvm::PrintModulePass::runOnModule(llvm::Module&) (PrintModulePass.h:41) ==12768== by 0xED6EB9: llvm::ModulePassManager::runPass(llvm::ModulePass*, llvm::Module*)...

The llvm_ostreams, which you take the address of go out of scope very quickly, and are only stored by address in the bytecode writer, thus the writers have a pointer to a stack allocated object they are to write to. This crashes. Andrew On 11/30/06, Rafael Espíndola <rafael.espindola at gmail.com> wrote: &...

...should be pretty transparent. There may be a few places which need a hack to support sstreams. This will be solved in the future. Here's what the changes are: Old Way New Way ------- ------- #include <iostream> #include "llvm/Support/Streams.h" or class llvm_ostream; // forward declaration std::cout llvm_cout std::cerr llvm_cerr std::cin llvm_cin DEBUG(std::cerr << "foo"); DOUT << "foo"; The changes are going to be gradual. I'll be checking them in over the next week. I'll send out more information about chan...