Displaying 6 results from an estimated 6 matches for "llvmtop".
Did you mean:
llvm_top
2006 Sep 28
1
[LLVMdev] Bug in WritingAnLLVMPass.html
...nLLVMPass-new.html 2006-09-28 21:06:36.000000000 +0800
@@ -1475,7 +1475,7 @@
want:</p>
<pre>
-(gdb) <b>break PassManager::run</b>
+(gdb) <b>break llvm::PassManager::run</b>
Breakpoint 1 at 0x2413bc: file Pass.cpp, line 70.
(gdb) <b>run test.bc -load $(LLVMTOP)/llvm/Debug/lib/[libname].so -[passoption]</b>
Starting program: opt test.bc -load $(LLVMTOP)/llvm/Debug/lib/[libname].so -[passoption]
2006 Sep 27
0
[LLVMdev] Name of Function's original module during link-time optimization
On Tue, 26 Sep 2006, Bram Adams wrote:
>
> A limitation here is that only Functions' debug data can be kept, as
> other Values (i.e. Instructions) are not Annotable. Is this an explicit
> design decision?
Yes, we intentionally do not want things to be annotatable. In fact,
Function being annotatable is a wart due to the way the code generator
currently works. In general, we
2006 Sep 26
2
[LLVMdev] Name of Function's original module during link-time optimization
Hi,
Chris Lattner wrote:
> I'd suggest writing a little pass that strips out debug intrinsics.
>
OK, I did this and it works (the strange seg fault also disappears after
all declared debug variables are gone)! In a first phase, all intrinsic
instructions are discarded after extracting their data into annotations
attached to the relevant Function. Then, a second phase wipes out the
2010 Jul 14
2
[LLVMdev] Trying to access the user defined variable name
...!2, metadata !"f",
metadata !"f", metadata !"f", metadata !2, i32 2, metadata !4, i1
false, i1 true, i32 0, i32 0, null, i1 false, i1 false} ; [
DW_TAG_subprogram ]
!2 = metadata !{i32 524329, metadata !"testadd.c", metadata
!"/home/asudarsanam/perforce/llvmtop/setup", metadata !3} ; [
DW_TAG_file_type ]
!3 = metadata !{i32 524305, i32 0, i32 12, metadata !"testadd.c",
metadata !".", metadata !"clang 2.0", i1 true, i1 false, metadata !"",
i32 0} ; [ DW_TAG_compile_unit ]
!4 = metadata !{i32 524309, metadata !2,...
2010 Jul 15
0
[LLVMdev] Trying to access the user defined variable name
...ot;,
> metadata !"f", metadata !"f", metadata !2, i32 2, metadata !4, i1
> false, i1 true, i32 0, i32 0, null, i1 false, i1 false} ; [
> DW_TAG_subprogram ]
> !2 = metadata !{i32 524329, metadata !"testadd.c", metadata
> !"/home/asudarsanam/perforce/llvmtop/setup", metadata !3} ; [
> DW_TAG_file_type ]
> !3 = metadata !{i32 524305, i32 0, i32 12, metadata !"testadd.c",
> metadata !".", metadata !"clang 2.0", i1 true, i1 false, metadata !"",
> i32 0} ; [ DW_TAG_compile_unit ]
> !4 = metadata !...
2010 Jul 15
2
[LLVMdev] Trying to access the user defined variable name
...ta !"f", metadata !"f", metadata !2, i32 2, metadata !4, i1
>> false, i1 true, i32 0, i32 0, null, i1 false, i1 false} ; [
>> DW_TAG_subprogram ]
>> !2 = metadata !{i32 524329, metadata !"testadd.c", metadata
>> !"/home/asudarsanam/perforce/llvmtop/setup", metadata !3} ; [
>> DW_TAG_file_type ]
>> !3 = metadata !{i32 524305, i32 0, i32 12, metadata !"testadd.c",
>> metadata !".", metadata !"clang 2.0", i1 true, i1 false, metadata !"",
>> i32 0} ; [ DW_TAG_compile_unit ]
>...