public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/97840] [11 regression] Bogus -Wmaybe-uninitialized
Date: Sun, 15 Nov 2020 18:03:24 +0000	[thread overview]
Message-ID: <bug-97840-4-NxEIXNW9US@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97840-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
And to explain why warning does not trigger without modref, it is because we
are not able to disambiguate the variable with another function call (since we
think it escapes)

(gdb) p debug_gimple_stmt (def_stmt)
# .MEM_7 = VDEF <.MEM_5>
_8 = __cxa_allocate_exception (48);

Martin, I think this is much more your area than mine.
I will post the patch on silencing warning on unused args, but I think we
shoulid resovle the empty field issue.

  parent reply	other threads:[~2020-11-15 18:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 16:14 [Bug middle-end/97840] New: " schwab@linux-m68k.org
2020-11-15 17:15 ` [Bug middle-end/97840] " hubicka at gcc dot gnu.org
2020-11-15 17:31 ` hubicka at gcc dot gnu.org
2020-11-15 17:57 ` hubicka at gcc dot gnu.org
2020-11-15 18:03 ` hubicka at gcc dot gnu.org [this message]
2020-11-16  1:22 ` msebor at gcc dot gnu.org
2020-11-16  7:27 ` rguenth at gcc dot gnu.org
2020-11-16  7:34 ` hubicka at gcc dot gnu.org
2020-11-16 15:32 ` cvs-commit at gcc dot gnu.org
2020-11-16 16:43 ` schwab@linux-m68k.org
2020-11-16 18:18 ` hubicka at gcc dot gnu.org
2020-11-16 20:11 ` jakub at gcc dot gnu.org
2020-11-16 20:18   ` Jan Hubicka
2020-11-16 20:18 ` hubicka at ucw dot cz
2020-11-16 20:30 ` jakub at gcc dot gnu.org
2020-11-16 20:37   ` Jan Hubicka
2020-11-16 20:37 ` hubicka at ucw dot cz
2020-11-16 21:54 ` msebor at gcc dot gnu.org
2020-11-16 22:01   ` Jan Hubicka
2020-11-16 22:01 ` hubicka at ucw dot cz
2020-11-17  3:02 ` cvs-commit at gcc dot gnu.org
2020-11-24  0:35 ` msebor 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-97840-4-NxEIXNW9US@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).