public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kees at outflux dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105539] -ftrivial-auto-var-init=zero happening too late?
Date: Tue, 10 May 2022 22:13:29 +0000	[thread overview]
Message-ID: <bug-105539-4-7umG4aYq9P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105539-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Kees Cook <kees at outflux dot net> ---
Right, perhaps I should rename this bug? The much more surprising thing is the
lack of warning about the uninit use. With or without -ftrivial-auto-var-init,
I'd want to have the diagnostic that a UB may have happened.

  parent reply	other threads:[~2022-05-10 22:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 18:27 [Bug c/105539] New: " kees at outflux dot net
2022-05-09 18:28 ` [Bug c/105539] " kees at outflux dot net
2022-05-09 18:33 ` kees at outflux dot net
2022-05-09 20:10 ` [Bug middle-end/105539] " pinskia at gcc dot gnu.org
2022-05-10  7:44 ` rguenth at gcc dot gnu.org
2022-05-10 16:35 ` qinzhao at gcc dot gnu.org
2022-05-10 16:40 ` qinzhao at gcc dot gnu.org
2022-05-10 22:13 ` kees at outflux dot net [this message]
2022-05-11  6:42 ` rguenth at gcc dot gnu.org
2022-05-11 14:09 ` qing.zhao at oracle dot com

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-105539-4-7umG4aYq9P@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: link
Be 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).