public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100250] [11/12 Regression] ICE related to -Wmaybe-uninitialized
Date: Mon, 26 Apr 2021 15:42:34 +0000	[thread overview]
Message-ID: <bug-100250-4-pFV0pEHbB6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100250-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
This is a consequence of fixing pr97172 by clearing the VLA bounds encoded by
the front end in function attributes before the IL enters the middle end: they
VLA bounds aren't used to decide whether to diagnose code but they are used in
the text of the warnings.  That's why the originally submitted patches
preserved them (v2 of the patch encoded them as strings:
https://gcc.gnu.org/pipermail/gcc-patches/2020-December/562318.html)

  parent reply	other threads:[~2021-04-26 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 20:44 [Bug tree-optimization/100250] New: " muecker at gwdg dot de
2021-04-26  7:26 ` [Bug tree-optimization/100250] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-04-26 15:42 ` msebor at gcc dot gnu.org [this message]
2021-04-26 15:48 ` msebor at gcc dot gnu.org
2021-04-26 23:31 ` msebor at gcc dot gnu.org
2021-04-29  1:12 ` cvs-commit at gcc dot gnu.org
2021-04-29  1:16 ` [Bug tree-optimization/100250] [11 " msebor at gcc dot gnu.org
2021-06-07 13:25 ` jakub at gcc dot gnu.org
2021-06-16 11:23 ` marxin at gcc dot gnu.org
2021-06-17 20:07 ` cvs-commit at gcc dot gnu.org
2021-06-17 20:09 ` 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-100250-4-pFV0pEHbB6@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).