similar to: [LLVMdev] does ENABLE_COVERAGE work?

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] does ENABLE_COVERAGE work?"

2016 Nov 20
3
uninitialized values in Attributes.cpp
I did a RelWithDebInfo + asserts build of LLVM just now and, when running "make check" under Valgrind, am seeing a lot of uses of uninitialized memory like the one below. Anyone know offhand what's likely to be the root cause? Unfortunately a Debug build doesn't give these errors. Thanks, John FAIL: LLVM :: Analysis/BasicAA/pr18573.ll (2093 of 18733)
2016 Nov 20
3
uninitialized values in Attributes.cpp
Well, it looks like almost all of the problems go away when I build using trunk instead of 3.9. So, that was scary but I'm going to forget it ever happened. >8000 test cases failed under Valgrind!! John On 11/20/2016 03:03 AM, Sanjoy Das via llvm-dev wrote: > Hi John, > > This is probably somewhat of a stretch, but since the problem does not > happen with a Debug build,
2016 Nov 20
2
uninitialized values in Attributes.cpp
> If 3.9 shipped with these issues (assuming these are not false positive), it would be interesting to 1) know why the sanitizers didn’t catch it, and 2) add valgrind to the release qualification process (CC Hans). Yes, I'd be interested to see some corroboration. Note that the issue here is pretty specific: it only happens during optimized compile using Clang-3.9. This is all I did:
2005 Dec 28
6
coverage does not work
Hi, I''ve installed coverage (gem install coverage) and try to run tests with -rcoverage option on, but following error occurs: ruby: No such file to load -- coverage (LoadError) I try: ruby -rcoverage mytest.rb 1. I have rubygems in evn var RUBYOPT 2. Gem seems to be installed properly (I can read doc via gems, the files exist in the ../gem/... dirs) Does anyone know what is the
2013 Mar 14
3
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
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',
2013 Mar 14
2
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
Thanks 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
2013 Mar 14
0
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
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
2013 Mar 15
2
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > Hi All, > > I think Nick's suggestion is correct, my code was linked against > libprofile_rt.a, which had gcda profiling code before, but was removed > https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff > > So, I couldn't find the correct symbols from
2013 Mar 19
2
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
Hi! On Fri, Mar 15, 2013 at 10:51 PM, Qun Fa <testforqunfa at gmail.com> wrote: > Thank you Alexey. > > I have tried to use Makefile. This will generate the correct symbols that > I need. > > Any idea on the schedule of adding CMake support to compiler-rt? > Starting from r177382 CMake on Linux should build the same profile compiler-rt library as Makefiles. >
2013 Mar 14
0
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
Hi All, I think Nick's suggestion is correct, my code was linked against libprofile_rt.a, which had gcda profiling code before, but was removed https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff So, I couldn't find the correct symbols from libprofile_rt.a any more. Now my assumption is I need to use the correct library that is provided by compiler-rt.
2008 Sep 03
3
[LLVMdev] Merge-Cha-Cha
As you all have undoubtedly noticed, I recently did Yet Another Merge to Apple's GCC top-of-tree. This merge was prompted by several important fixes in the "blocks" implementation. There are still many testcases that need to be moved over, but those can come at our leisure. I compiled both the "Apple way" and the "FSF way". It also passed the tests in
2016 Apr 06
2
Writing a test for gcov style coverage crashing after dlclose
Hi Everyone, I have uploaded a patch that allows one to successfully gather gcov/gcda coverage information on programs which unload shared libraries. It¹s a simple fix, just adding a few COMPILER_RT_VISIBILITY (i.e. __attribute__((visibility("hidden")))) in GCDAProfiling.c. Now, I¹d like to include a test program to demonstrate the fix. AFAICT, there seems to be a single test for
2013 Mar 15
0
[LLVMdev] undefined reference to 'llvm_gcda_start_file', 'llvm_gcda_emit_arcs', etc
Thank you Alexey. I have tried to use Makefile. This will generate the correct symbols that I need. Any idea on the schedule of adding CMake support to compiler-rt? Sincerely, Qun On Fri, Mar 15, 2013 at 1:51 AM, Alexey Samsonov <samsonov at google.com>wrote: > > On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > >> Hi All, >>
2008 Oct 02
1
[LLVMdev] build broken (a different way)
I get the output below on Ubuntu Hardy on ia32 from svn 56984. John make[2]: Entering directory `/home/regehr/llvm-gcc/build/gcc' /home/regehr/llvm-gcc/build/./gcc/xgcc -B/home/regehr/llvm-gcc/build/./gcc/ -B/home/regehr/i686-pc-linux-gnu/bin/ -B/home/regehr/i686-pc-linux-gnu/lib/ -isystem /home/regehr/i686-pc-linux-gnu/include -isystem /home/regehr/i686-pc-linux-gnu/sys-include -O2 -O2
2008 Sep 03
0
[LLVMdev] Merge-Cha-Cha
I'm getting the error below on Ubuntu Hardy on ia32 on r55688. John make[3]: Entering directory `/home/regehr/llvm-gcc/build/gcc' gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc
2015 Jul 22
8
[LLVMdev] some superoptimizer results
We (the folks working on Souper) would appreciate any feedback on these IR-level superoptimizer results: http://blog.regehr.org/extra_files/souper-jul-15.html My impression is that while there's clearly plenty of material in here that doesn't want to get implemented in an opt pass, there are a number of gems hiding in there that are worth implementing. Blog post containing
2014 Nov 25
3
[LLVMdev] new set of superoptimizer results
Cool! Looks like we do lots of provably unnecessary alignment checks. :) On Tue, Nov 25, 2014 at 9:03 AM, John Regehr <regehr at cs.utah.edu> wrote: > Actually, let me save you some time by pointing out the thing that is > perhaps immediately useful about our recent work, which is the fact that > Souper now supports "optimization profiling". > > If you build an
2008 Sep 11
1
[LLVMdev] linux llvm-gcc build broken
See below. This is on Ubuntu Hardy on ia32. Thanks, John make[3]: Entering directory `/home/regehr/llvm-gcc/build/gcc' gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/.
2008 Apr 23
3
[LLVMdev] problem building llvm + 4.2 frontend from svn
I checked out LLVM and configured like this: ./configure --prefix=/home/regehr --enable-optimized then built and installed it. Then, checked out the frontend, configured like this: ../configure --prefix=/home/regehr --enable-languages=c,c++ \ --enable-llvm=/home/regehr/z/llvm but when I try to build I get configure: error: You must specify valid path to your LLVM tree with
2009 Jan 20
3
[LLVMdev] linux build problem
Since yesterday I've been getting the error below when building llvm-gcc on Ubuntu Hardy on x86. For some reason, several instances of autoconf are getting confused and failing to detect a stdlib.h. John /home/regehr/z/tmp/llvm-gcc-r62547-src/build/./prev-gcc/xgcc -B/home/regehr/z/tmp/llvm-gcc-r62547-src/build/./prev-gcc/