Displaying 3 results from an estimated 3 matches for "suganuma".
2016 Mar 09
3
PGO question
..., the resulting bitcode seems
to cause a problem as follows (my environment is 3.9.0, mid Feb trunk).
$ clang -c -o main.bc -O2 -m64 -emit-llvm main.c
$ opt -pgo-instr-gen main.bc -o main_inst.bc
$ llc main_inst.bc -o main_inst.s
instrprof failed to lower an increment
UNREACHABLE executed
at /home/suganuma/tools/llvm_new/llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp:5245!
#0 0x00000000815ecc7a llvm::sys::PrintStackTrace
(llvm::raw_ostream&) /home/suganuma/tools/llvm_new/llvm/lib/Support/Unix/Signals.inc:322:0
#1 0x00000000815ed02a PrintStackTraceSignalHandler
(void*) /home/suganuma/tools/...
2016 Mar 22
3
Instrumented BB in PGO
Hello,
I have a question regarding PGO instrumented BBs (I use IR-level
instrumentation).
It seems that instrumented BBs do not match between the two compilations
for profile-gen and profile-use for some cases. Here is an example from
SPECcpu 2006 lbm (a simple case consisting of just two modules).
In the first compilation, we have 5 instrumentation points for the main
function as follows:
$
2016 Mar 07
3
Profile-based inlining status
Hello,
I'm learning how LLVM performs PGO (profile-guided optimizations) by using
the instrumentation-based profile build (-fprofile-instr-generate and
-fprofile-instr-use).
However, I found there is no difference in inlining behaviors between with
and without PGO for a few spec benchmarks by checking the emit optimization
reports (-Rpass=inline -Rpass-missed=inline -Rpass-analysis=inline).