public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105689] Bogus `-Wstringop-overflow=` after accessing field, then containing struct (wrong "region size")
Date: Mon, 23 May 2022 07:30:44 +0000 [thread overview]
Message-ID: <bug-105689-4-e0bCMQD7zK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105689-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105689
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Keywords| |diagnostic
Known to fail| |11.2.0, 12.1.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's likely triggered by us CSEing &me->sub.field1 and &me->sub but I don't
know how that changes whether a diagnostic happens or not. Hmm, IIRC there's
some magic going on at the frontend which attaches some further attributes
which
then _might_ get confused with such CSE.
Martin, do you remember off-head how such CSE might impact the diagnostics?
next prev parent reply other threads:[~2022-05-23 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 11:30 [Bug c/105689] New: " sagebar at web dot de
2022-05-23 7:30 ` rguenth at gcc dot gnu.org [this message]
2022-05-23 20:27 ` [Bug c/105689] " msebor at gcc dot gnu.org
2023-05-17 20:56 ` [Bug tree-optimization/105689] " pinskia at gcc dot gnu.org
2023-05-17 21:00 ` 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-105689-4-e0bCMQD7zK@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).