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 ipa/105438] [11/12/13 Regression] Incorrect array-bounds warning with array size carried over from a previous template instantiation
Date: Mon, 02 May 2022 06:57:49 +0000 [thread overview]
Message-ID: <bug-105438-4-Of6CLKNnFs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105438-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105438
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.4
Summary|Incorrect array-bounds |[11/12/13 Regression]
|warning with array size |Incorrect array-bounds
|carried over from a |warning with array size
|previous template |carried over from a
|instantiation |previous template
| |instantiation
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> It's IPA ICF that merges the two functions. We then end up inlining but not
> using the original function body but the merged one.
I wonder if we could get wrong code because of that ...
next prev parent reply other threads:[~2022-05-02 6:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 8:24 [Bug c++/105438] New: " bernie at codewiz dot org
2022-04-30 8:27 ` [Bug c++/105438] " bernie at codewiz dot org
2022-05-02 6:05 ` bernie at codewiz dot org
2022-05-02 6:07 ` bernie at codewiz dot org
2022-05-02 6:11 ` bernie at codewiz dot org
2022-05-02 6:54 ` [Bug ipa/105438] " rguenth at gcc dot gnu.org
2022-05-02 6:57 ` pinskia at gcc dot gnu.org [this message]
2022-05-03 12:27 ` [Bug ipa/105438] [11/12/13 Regression] Incorrect array-bounds warning with array size carried over from a previous template instantiation since r11-4987-g602c6cfc79ce4ae6 since r11-4987-g602c6cfc79ce4ae6 marxin at gcc dot gnu.org
2022-05-03 12:42 ` marxin at gcc dot gnu.org
2022-07-26 11:39 ` [Bug ipa/105438] [11/12/13 Regression] Incorrect array-bounds warning with array size carried over from a previous template instantiation " rguenth at gcc dot gnu.org
2023-01-22 0:55 ` bernie at codewiz dot org
2023-02-09 11:37 ` marxin at gcc dot gnu.org
2023-05-29 10:06 ` [Bug ipa/105438] [11/12/13/14 " jakub at gcc dot gnu.org
2023-07-20 7:23 ` bernie at codewiz dot org
2023-07-27 9:22 ` rguenth 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-105438-4-Of6CLKNnFs@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).