Displaying 4 results from an estimated 4 matches for "asmoutfil".
Did you mean:
asmoutfile
2006 Dec 01
0
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
...able.
>
Hey guys,
Notice that the llvm_ostream doesn't delete the ostream that you pass
into it. If you want to make sure that it's deleted, I think you'll
want to pass in "true" to the WriteBytecodePass so that it'll delete
the llvm_ostream. This won't affect the AsmOutFile, which gets deleted
at the end of the function...
-bw
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 correctly,
2006 Dec 01
0
[LLVMdev] [patch] [llvm-gcc4] fix bootstrap failure
...t;
> Notice that the llvm_ostream doesn't delete the ostream that you pass
> into it. If you want to make sure that it's deleted, I think you'll
> want to pass in "true" to the WriteBytecodePass so that it'll delete
> the llvm_ostream. This won't affect the AsmOutFile, which gets deleted
> at the end of the function...
>
> -bw
>
2007 Apr 30
1
[LLVMdev] llvm-gcc build broken
...#39; was not declared in this scope
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:209: error: `cerr' was
not declared in this scope
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp: In function `void
llvm_pch_write_init()':
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:226: error:
`AsmOutFile' was not declared in this scope
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:226: error: expected
type-specifier before `OStream'
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:226: error: expected
`;' before `OStream'
/projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:228: e...