This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[go]: Many valgrind errors (use of uninit value, jump depends on uninit value) in the testsuite
- From: Uros Bizjak <ubizjak at gmail dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: Mike Stump <mikestump at comcast dot net>, Rainer Orth <ro at cebitec dot uni-bielefeld dot de>, gcc-patches at gcc dot gnu dot org, gofrontend-dev at googlegroups dot com
- Date: Thu, 7 Jul 2011 14:18:31 +0200
- Subject: [go]: Many valgrind errors (use of uninit value, jump depends on uninit value) in the testsuite
On Tue, Jul 5, 2011 at 10:12 PM, Ian Lance Taylor <iant@google.com> wrote:
>> What remains is a couple of unrelated failures in the testsuite:
>> ../../../gcc-svn/trunk/libgo/testsuite/gotest: line 388: 13945
>> Segmentation fault ? ? ?./a.out -test.short -test.timeout=$timeout
>> "$@"
>> FAIL: compress/flate
>> gmake[2]: *** [compress/flate/check] Error 1
>>
>> Any ideas how to attack these?
>
> None of these look familiar to me.
compress/flate test sometimes passes and sometimes don't. I have run
the resulting executable through the valgrind, and there are many
(i.e. hundreds) of warnings of uses and calls that depend on
uninitialized variables, also on x86_64.
ATM, I would like to just report problems with valgrind, and due to
the number of them, it looks to me that something is wrong with the
library.
Uros.