public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/63311] [9/10/11/12 Regression] -O1 optimization introduces valgrind warning Date: Tue, 15 Feb 2022 12:09:54 +0000 [thread overview] Message-ID: <bug-63311-4-cl2yZX28Fr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311 Mark Wielaard <mark at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at gcc dot gnu.org --- Comment #19 from Mark Wielaard <mark at gcc dot gnu.org> --- This still replicates with valgrind 3.18.1 and gcc 11.2.1: $ gcc -O1 -std=c11 -g PR63311.c -lm && valgrind --track-origins=yes ./a.out ==2836066== Memcheck, a memory error detector ==2836066== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==2836066== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==2836066== Command: ./a.out ==2836066== ==2836066== Conditional jump or move depends on uninitialised value(s) ==2836066== at 0x4011E2: test (PR63311.c:41) ==2836066== by 0x401223: main (PR63311.c:130) ==2836066== Uninitialised value was created by a stack allocation ==2836066== at 0x40112D: test (PR63311.c:11) ==2836066== ==2836066== ==2836066== HEAP SUMMARY: ==2836066== in use at exit: 0 bytes in 0 blocks ==2836066== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==2836066== ==2836066== All heap blocks were freed -- no leaks are possible ==2836066== ==2836066== For lists of detected and suppressed errors, rerun with: -s ==2836066== ERROR SUMMARY: 4 errors from 1 contexts (suppressed: 0 from 0)
next prev parent reply other threads:[~2022-02-15 12:09 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-19 15:03 [Bug middle-end/63311] New: [4.9/5 " Joost.VandeVondele at mat dot ethz.ch 2014-09-22 10:24 ` [Bug middle-end/63311] " rguenth at gcc dot gnu.org 2014-09-22 10:24 ` rguenth at gcc dot gnu.org 2014-09-22 10:34 ` dominiq at lps dot ens.fr 2014-10-09 9:45 ` jakub at gcc dot gnu.org 2014-10-30 10:42 ` jakub at gcc dot gnu.org 2014-10-31 9:30 ` Joost.VandeVondele at mat dot ethz.ch 2014-10-31 9:34 ` Joost.VandeVondele at mat dot ethz.ch 2014-11-24 13:27 ` rguenth at gcc dot gnu.org 2014-11-24 13:54 ` Joost.VandeVondele at mat dot ethz.ch 2015-06-26 20:12 ` [Bug middle-end/63311] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:36 ` jakub at gcc dot gnu.org 2021-05-14 9:47 ` [Bug middle-end/63311] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-02-15 12:09 ` mark at gcc dot gnu.org [this message] 2022-02-16 22:49 ` dmalcolm at gcc dot gnu.org 2022-02-17 2:41 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:35 ` [Bug middle-end/63311] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug middle-end/63311] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-09-03 3:39 ` [Bug middle-end/63311] [11/12 " pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-63311-4-cl2yZX28Fr@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).