search for: llvm_start_basic_block_trac

..._increment_indirect_counter 0000000000000a80 S _llvm_gcda_increment_indirect_counter.eh 0000000000000000 T _llvm_gcda_start_file 0000000000000a08 S _llvm_gcda_start_file.eh They are the symbols that my test build is looking for. But with the latest codebase, here is what I saw 00000000000000a8 T llvm_start_basic_block_tracing 0000000000000067 T llvm_trace_basic_block 0000000000000467 T llvm_decrement_path_count 000000000000042a T llvm_increment_path_count 0000000000000662 T llvm_start_path_profiling 0000000000000020 T llvm_start_edge_profiling 0000000000000020 T llvm_start_opt_edge_profiling Thanks again, Qun On Th...

...ndirect_counter.eh >> 0000000000000000 T _llvm_gcda_start_file >> 0000000000000a08 S _llvm_gcda_start_file.eh >> >> They are the symbols that my test build is looking for. >> >> But with the latest codebase, here is what I saw >> >> 00000000000000a8 T llvm_start_basic_block_tracing >> 0000000000000067 T llvm_trace_basic_block >> 0000000000000467 T llvm_decrement_path_count >> 000000000000042a T llvm_increment_path_count >> 0000000000000662 T llvm_start_path_profiling >> 0000000000000020 T llvm_start_edge_profiling >> 0000000000000020 T l...

...0000a80 S _llvm_gcda_increment_indirect_counter.eh > 0000000000000000 T _llvm_gcda_start_file > 0000000000000a08 S _llvm_gcda_start_file.eh > > They are the symbols that my test build is looking for. > > But with the latest codebase, here is what I saw > > 00000000000000a8 T llvm_start_basic_block_tracing > 0000000000000067 T llvm_trace_basic_block > 0000000000000467 T llvm_decrement_path_count > 000000000000042a T llvm_increment_path_count > 0000000000000662 T llvm_start_path_profiling > 0000000000000020 T llvm_start_edge_profiling > 0000000000000020 T llvm_start_opt_edge_profi...

...a_start_file >>>> 0000000000000a08 S _llvm_gcda_start_file.eh >>>> >>>> They are the symbols that my test build is looking for. >>>> >>>> But with the latest codebase, here is what I saw >>>> >>>> 00000000000000a8 T llvm_start_basic_block_tracing >>>> 0000000000000067 T llvm_trace_basic_block >>>> 0000000000000467 T llvm_decrement_path_count >>>> 000000000000042a T llvm_increment_path_count >>>> 0000000000000662 T llvm_start_path_profiling >>>> 0000000000000020 T llvm_start_edge...

...0000000000000000 T _llvm_gcda_start_file >>> 0000000000000a08 S _llvm_gcda_start_file.eh >>> >>> They are the symbols that my test build is looking for. >>> >>> But with the latest codebase, here is what I saw >>> >>> 00000000000000a8 T llvm_start_basic_block_tracing >>> 0000000000000067 T llvm_trace_basic_block >>> 0000000000000467 T llvm_decrement_path_count >>> 000000000000042a T llvm_increment_path_count >>> 0000000000000662 T llvm_start_path_profiling >>> 0000000000000020 T llvm_start_edge_profiling >>&...

...;> 0000000000000a08 S _llvm_gcda_start_file.eh >>>>> >>>>> They are the symbols that my test build is looking for. >>>>> >>>>> But with the latest codebase, here is what I saw >>>>> >>>>> 00000000000000a8 T llvm_start_basic_block_tracing >>>>> 0000000000000067 T llvm_trace_basic_block >>>>> 0000000000000467 T llvm_decrement_path_count >>>>> 000000000000042a T llvm_increment_path_count >>>>> 0000000000000662 T llvm_start_path_profiling >>>>> 00000000000000...

..._llvm_gcda_start_file.eh >>>>>> >>>>>> They are the symbols that my test build is looking for. >>>>>> >>>>>> But with the latest codebase, here is what I saw >>>>>> >>>>>> 00000000000000a8 T llvm_start_basic_block_tracing >>>>>> 0000000000000067 T llvm_trace_basic_block >>>>>> 0000000000000467 T llvm_decrement_path_count >>>>>> 000000000000042a T llvm_increment_path_count >>>>>> 0000000000000662 T llvm_start_path_profiling >>>>&gt...

Thanks Chris, but the method you mentioned is not what I want. Maybe I didn't make it clear. As you said, /runtime/libprofile is runtime library for the following function. llvm_start_func_profiling llvm_start_block_profiling llvm_start_basic_block_tracing llvm_trace_basic_block And those above functions can be inserted into basic block etc for getting profile. However, those functions are wroten by C/C++ which just statistic some data. What I want is to write a Pass in external library. You know for the Pass, it will use LLVM methods. I can...

...s. I see in the utils/profile.pl there are supports for "-insert-block-profiling", "-insert-edge-profiling" and "-insert-function-profiling", but it seems only -insert-edge-profiling is working and the other 2 gets suggested to "-insert-gcov-profiling". and llvm_start_basic_block_tracing does not seem to be called anywhere in the LLVM src code. Thank you, Trent -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130926/10641079/attachment.html>

Qun Fa wrote: > Hi, > I am trying to test my project and get the code coverage with a version > of clang compiler that was built from the latest llvm/clang codebase. > > It worked for a while. But today, after I updated my local checkout, and > re-build llvm, clang and compiler-rt, when I test my project again, I > got the errors with undefined reference to

Hi, I am trying to test my project and get the code coverage with a version of clang compiler that was built from the latest llvm/clang codebase. It worked for a while. But today, after I updated my local checkout, and re-build llvm, clang and compiler-rt, when I test my project again, I got the errors with undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs',

...counter.eh > > 0000000000000000 T _llvm_gcda_start_file > > 0000000000000a08 S _llvm_gcda_start_file.eh > > > > They are the symbols that my test build is looking for. > > > > But with the latest codebase, here is what I saw > > > > 00000000000000a8 T llvm_start_basic_block_tracing > > 0000000000000067 T llvm_trace_basic_block > > 0000000000000467 T llvm_decrement_path_count > > 000000000000042a T llvm_increment_path_count > > 0000000000000662 T llvm_start_path_profiling > > 0000000000000020 T llvm_start_edge_profiling > > 00000000000000...