search for: llvm_gcda_emit_arcs

...rsion 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', 'llvm_gcda_emit_function', and 'llvm_gcda_end_file'. I have searched the codebase, and have found the functions are defined in GCDAProfiling.c file, but not sure why this suddenly doesn't work for me. Anyone can give any suggestions? Thanks very much in advance. Qun ---...

...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', 'llvm_gcda_emit_function', and 'llvm_gcda_end_file'. > > I have searched the codebase, and have found the functions are defined > in GCDAProfiling.c file, but not sure why this suddenly doesn't work for me. > > Anyone can give any suggestions? Those symbols...

Hi, I've been seeing a crash in llvm_gcda_emit_arcs() on x86_64. The crash occurs executing a movdqa instruction with an unaligned src address. The attached patch to the compiler-rt project fixes the problem by using memcpy() to read data from the write_buffer[] in GCDAProfiling.c. This is my first patch submission to llvm so please let me know i...

Bill, could you take a look at this? I don't have a checkout of compiler-rt that builds. It seems obviously-correct to me, but I wish it did a compare against cur_buffer_size to make sure it's in range. Nick Joseph Kain wrote: > Hi, > > I've been seeing a crash in llvm_gcda_emit_arcs() on x86_64. The crash > occurs executing a movdqa instruction with an unaligned src address. > The attached patch to the compiler-rt project fixes the problem by > using memcpy() to read data from the write_buffer[] in GCDAProfiling.c. > > This is my first patch submission to llv...

...at builds. >> >> It seems obviously-correct to me, but I wish it did a compare against >> cur_buffer_size to make sure it's in range. >> >> Nick >> >> Joseph Kain wrote: >> >>> Hi, >>> >>> I've been seeing a crash in llvm_gcda_emit_arcs() on x86_64. The crash >>> occurs executing a movdqa instruction with an unaligned src address. >>> The attached patch to the compiler-rt project fixes the problem by >>> using memcpy() to read data from the write_buffer[] in GCDAProfiling.c. >>> >>>...

...#39;t have a checkout of > compiler-rt that builds. > > It seems obviously-correct to me, but I wish it did a compare against > cur_buffer_size to make sure it's in range. > > Nick > > Joseph Kain wrote: > >> Hi, >> >> I've been seeing a crash in llvm_gcda_emit_arcs() on x86_64. The crash >> occurs executing a movdqa instruction with an unaligned src address. >> The attached patch to the compiler-rt project fixes the problem by >> using memcpy() to read data from the write_buffer[] in GCDAProfiling.c. >> >> This is my first pat...

...ommended library that should be linked against? > > I am currently linking libprofile_rt.a. > > And I have noticed the differences that, if we do > > `nm libprofile_rt.a | grep llvm` > > with my old copy of the llvm/clang installation, I can see > > 00000000000005e0 T _llvm_gcda_emit_arcs > 0000000000000b48 S _llvm_gcda_emit_arcs.eh > 0000000000000430 T _llvm_gcda_emit_function > 0000000000000aa8 S _llvm_gcda_emit_function.eh > 00000000000006c0 T _llvm_gcda_end_file > 0000000000000b98 S _llvm_gcda_end_file.eh > 00000000000003d0 T _llvm_gcda_increment_indirect_count...

...for your reply. May I know which is the recommended library that should be linked against? I am currently linking libprofile_rt.a. And I have noticed the differences that, if we do `nm libprofile_rt.a | grep llvm` with my old copy of the llvm/clang installation, I can see 00000000000005e0 T _llvm_gcda_emit_arcs 0000000000000b48 S _llvm_gcda_emit_arcs.eh 0000000000000430 T _llvm_gcda_emit_function 0000000000000aa8 S _llvm_gcda_emit_function.eh 00000000000006c0 T _llvm_gcda_end_file 0000000000000b98 S _llvm_gcda_end_file.eh 00000000000003d0 T _llvm_gcda_increment_indirect_counter 0000000000000a80 S _llvm_gc...

...urrently linking libprofile_rt.a. >>> >>> And I have noticed the differences that, if we do >>> >>> `nm libprofile_rt.a | grep llvm` >>> >>> with my old copy of the llvm/clang installation, I can see >>> >>> 00000000000005e0 T _llvm_gcda_emit_arcs >>> 0000000000000b48 S _llvm_gcda_emit_arcs.eh >>> 0000000000000430 T _llvm_gcda_emit_function >>> 0000000000000aa8 S _llvm_gcda_emit_function.eh >>> 00000000000006c0 T _llvm_gcda_end_file >>> 0000000000000b98 S _llvm_gcda_end_file.eh >>> 000000...

...gainst? >> >> I am currently linking libprofile_rt.a. >> >> And I have noticed the differences that, if we do >> >> `nm libprofile_rt.a | grep llvm` >> >> with my old copy of the llvm/clang installation, I can see >> >> 00000000000005e0 T _llvm_gcda_emit_arcs >> 0000000000000b48 S _llvm_gcda_emit_arcs.eh >> 0000000000000430 T _llvm_gcda_emit_function >> 0000000000000aa8 S _llvm_gcda_emit_function.eh >> 00000000000006c0 T _llvm_gcda_end_file >> 0000000000000b98 S _llvm_gcda_end_file.eh >> 00000000000003d0 T _llvm_gcda_...

...gt;>> And I have noticed the differences that, if we do >>>>> >>>>> `nm libprofile_rt.a | grep llvm` >>>>> >>>>> with my old copy of the llvm/clang installation, I can see >>>>> >>>>> 00000000000005e0 T _llvm_gcda_emit_arcs >>>>> 0000000000000b48 S _llvm_gcda_emit_arcs.eh >>>>> 0000000000000430 T _llvm_gcda_emit_function >>>>> 0000000000000aa8 S _llvm_gcda_emit_function.eh >>>>> 00000000000006c0 T _llvm_gcda_end_file >>>>> 0000000000000b98 S _l...

...oticed the differences that, if we do >>>>>> >>>>>> `nm libprofile_rt.a | grep llvm` >>>>>> >>>>>> with my old copy of the llvm/clang installation, I can see >>>>>> >>>>>> 00000000000005e0 T _llvm_gcda_emit_arcs >>>>>> 0000000000000b48 S _llvm_gcda_emit_arcs.eh >>>>>> 0000000000000430 T _llvm_gcda_emit_function >>>>>> 0000000000000aa8 S _llvm_gcda_emit_function.eh >>>>>> 00000000000006c0 T _llvm_gcda_end_file >>>>>> 0...

.... >>>> >>>> And I have noticed the differences that, if we do >>>> >>>> `nm libprofile_rt.a | grep llvm` >>>> >>>> with my old copy of the llvm/clang installation, I can see >>>> >>>> 00000000000005e0 T _llvm_gcda_emit_arcs >>>> 0000000000000b48 S _llvm_gcda_emit_arcs.eh >>>> 0000000000000430 T _llvm_gcda_emit_function >>>> 0000000000000aa8 S _llvm_gcda_emit_function.eh >>>> 00000000000006c0 T _llvm_gcda_end_file >>>> 0000000000000b98 S _llvm_gcda_end_file.eh...

...ow the GCDA based profiling to work correctly with code using dlopen/dlclose to load and unload shared libraries. Each shared library must have its own copy of the following GCDA functions: - __gcov_flush - llvm_delete_flush_function_list - llvm_delete_writeout_function_list - llvm_gcda_emit_arcs - llvm_gcda_emit_function - llvm_gcda_end_file - llvm_gcda_increment_indirect_counter - llvm_gcda_start_file - llvm_gcda_summary_info - llvm_gcov_init - llvm_register_flush_function - llvm_register_writeout_function - llvm_writeout_files Defining these...

...) > 3. Re: Suggestion About Adding Target Dependent Decision in LSR > Please (Yin Ma) > 4. Re: Suggestion About Adding Target Dependent Decision in LSR > Please (Hal Finkel) > 5. Re: undefined reference to 'llvm_gcda_start_file', > 'llvm_gcda_emit_arcs', etc (Qun Fa) > 6. Re: Suggestion About Adding Target Dependent Decision in LSR > Please (Yin Ma) > 7. Problems about developing LLVM pass on windows visual studio > (tianxiang sui) > 8. Re: Problems about developing LLVM pass on windows visual...