public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108980] [13 Regression] Warning text missing the warning itself (GCC 13)
Date: Wed, 01 Mar 2023 04:26:59 +0000 [thread overview]
Message-ID: <bug-108980-4-dEVdNb0QzP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108980-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108980
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Warning text missing the |[13 Regression] Warning
|warning itself (GCC 13) |text missing the warning
| |itself (GCC 13)
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The logic is:
if (warned || out_of_bound)
{
if ((out_of_bound && warn_strict_flex_arrays)
&& (((sam == special_array_member::trail_0)
|| (sam == special_array_member::trail_1)
|| (sam == special_array_member::trail_n))
&& DECL_NOT_FLEXARRAY (afield_decl)))
warned = warning_at (location,
...
if (DECL_P (ref))
inform (DECL_SOURCE_LOCATION (ref), "while referencing %qD", ref);
if (rec && DECL_P (rec))
inform (DECL_SOURCE_LOCATION (rec), "defined here %qD", rec);
The checks before calling inform should include a check for warned .
Started with r13-4748-g2a27ae32fabf85 .
next prev parent reply other threads:[~2023-03-01 4:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 4:18 [Bug c++/108980] New: " thiago at kde dot org
2023-03-01 4:19 ` [Bug c++/108980] " thiago at kde dot org
2023-03-01 4:20 ` [Bug tree-optimization/108980] " pinskia at gcc dot gnu.org
2023-03-01 4:26 ` pinskia at gcc dot gnu.org [this message]
2023-03-01 4:27 ` [Bug tree-optimization/108980] [13 Regression] " pinskia at gcc dot gnu.org
2023-03-01 4:27 ` pinskia at gcc dot gnu.org
2023-03-01 7:54 ` rguenth at gcc dot gnu.org
2023-03-01 18:02 ` thiago at kde dot org
2023-03-01 18:34 ` thiago at kde dot org
2023-03-01 18:46 ` pinskia at gcc dot gnu.org
2023-03-01 19:05 ` thiago at kde dot org
2023-03-01 20:16 ` pinskia at gcc dot gnu.org
2023-03-01 23:27 ` pinskia at gcc dot gnu.org
2023-03-09 18:04 ` pinskia at gcc dot gnu.org
2023-03-09 18:28 ` cvs-commit at gcc dot gnu.org
2023-03-09 18:29 ` 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-108980-4-dEVdNb0QzP@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).