Displaying 4 results from an estimated 4 matches for "bytecodefil".
Did you mean:
bytecodefile
2007 Sep 10
2
[LLVMdev] profiling with llvm-gcc4?
How can I do function profiling and BB profiling with current llvm and
llvm-gcc4?
runtime/libprofile is disabled when using llvm-gcc4, but... is there any
alternative to linking with libprofile_rt.so?
How can I use llvm-prof? is utils/profile.pl obsolete?
Thanks in advance,
josem
2007 Sep 10
0
[LLVMdev] profiling with llvm-gcc4?
On Mon, 10 Sep 2007, Jose M. Moya wrote:
> How can I do function profiling and BB profiling with current llvm and
> llvm-gcc4?
>
> runtime/libprofile is disabled when using llvm-gcc4, but... is there any
> alternative to linking with libprofile_rt.so?
>
> How can I use llvm-prof? is utils/profile.pl obsolete?
The profiling support in LLVM hasn't been used for quite a
2007 Sep 11
1
[LLVMdev] profiling with llvm-gcc4?
...$LLIPath = `which lli`;
-$LLIPath = `dirname $LLIPath`;
-chomp $LLIPath;
+my $libdir = `llvm-config --libdir`;
+chomp $libdir;
-my $LibProfPath = $LLIPath . "/../../Debug/lib/profile_rt.so";
+my $LibProfPath = $libdir . "/profile_rt.so";
system "opt -q -f $ProfilePass $BytecodeFile -o $BytecodeFile.inst";
system "lli -fake-argv0 '$BytecodeFile' -load $LibProfPath " .
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
Here is the bulk of the sanitizing.
My residual doubts center around the question
whether we still do/want to support (un)compressed *byte*code
in 2.0/2.1.
I need a definitive word on this to proceed.
My understanding is that bytecode is already gone, but there are
still some functions/enums that really deal with *byte*code
(instead of *bit*code).
I did not touch those areas, so the attached