Displaying 7 results from an estimated 7 matches for "llvm_ostreams".
2006 Nov 30
3
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
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 co...
2006 Dec 01
0
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
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 wo...
2006 Dec 01
0
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
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 out...
2006 Nov 30
3
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
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>
2006 Nov 30
0
[LLVMdev] Conditional jump or move depends on uninitialised value
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:
2006 Nov 30
0
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
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:
&g...
2006 Nov 27
0
[LLVMdev] Change in I/O Streams
Hi all,
There is going to be a sweeping change in how the I/O streams are
used. We'll no longer be using std::cout, std::cerr, std::cin, etc.
in each file. Instead, new LLVM streams will be used. The reason for
this is because each "#include <iostream>" introduces an overhead in
each compilation unit due to it needing to make sure that all of the
std::c* streams are