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 c/105150] [9/10/11/12 Regression] ICE with -Ofast: verify_gimple failed
Date: Tue, 05 Apr 2022 09:30:22 +0000 [thread overview]
Message-ID: <bug-105150-4-ai4ykIN4Fz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105150-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105150
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |c
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> IMHO that's a frontend problem - it should not do that.
Yes I think when we go and merge the builtin and the user supplied
(un-prototyped) decl, we should handle it similar to argument missmatch wtih
respect to not copying the builtins info.
next prev parent reply other threads:[~2022-04-05 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 16:43 [Bug c/105150] New: " gscfq@t-online.de
2022-04-04 17:16 ` [Bug tree-optimization/105150] " jakub at gcc dot gnu.org
2022-04-04 17:58 ` jakub at gcc dot gnu.org
2022-04-05 6:52 ` rguenth at gcc dot gnu.org
2022-04-05 9:21 ` rguenth at gcc dot gnu.org
2022-04-05 9:30 ` pinskia at gcc dot gnu.org [this message]
2022-04-06 8:13 ` [Bug c/105150] " cvs-commit at gcc dot gnu.org
2022-04-06 14:49 ` cvs-commit at gcc dot gnu.org
2022-04-07 7:13 ` cvs-commit at gcc dot gnu.org
2022-04-07 7:20 ` [Bug c/105150] [9/10/11 " jakub at gcc dot gnu.org
2022-04-07 7:21 ` rguenther at suse dot de
2022-05-27 9:47 ` [Bug c/105150] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07 10:42 ` [Bug c/105150] [11 " rguenth at gcc dot gnu.org
2024-03-10 4:39 ` 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-105150-4-ai4ykIN4Fz@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).