This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug middle-end/63311] [6/7/8 Regression] -O1 optimization introduces valgrind warning


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2014-09-22 00:00:00         |2018-2-5
                 CC|                            |aldyh at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org

--- Comment #12 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Reconfirmed with C testcase in comment 6.  However, as per Richard's comment in
#7, is this a WONTFIX?

tor:~/bld/t/gcc$ valgrind ./a.out
==29746== Memcheck, a memory error detector
==29746== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==29746== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==29746== Command: ./a.out
==29746== 
==29746== Conditional jump or move depends on uninitialised value(s)
==29746==    at 0x40068C: test (a.c:41)
==29746==    by 0x4006CC: main (a.c:130)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]