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/111816] ICE with _GIMPLE and 2 returns
Date: Sun, 15 Oct 2023 01:26:30 +0000 [thread overview]
Message-ID: <bug-111816-4-fdZ4qUeW6b@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111816-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111816
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Summary|GCC: 14: internal compiler |ICE with _GIMPLE and 2
|error: Segmentation fault |returns
|at |
|c_parser_parse_gimple_body |
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note even though the gimple FE exists, it is mainly designed ONLY for testsuite
usage and that there will be many corner cases like this where code will cause
an ICE rather than be rejected for being invalid.
next prev parent reply other threads:[~2023-10-15 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 1:21 [Bug c/111816] New: GCC: 14: internal compiler error: Segmentation fault at c_parser_parse_gimple_body 141242068 at smail dot nju.edu.cn
2023-10-15 1:26 ` pinskia at gcc dot gnu.org [this message]
2023-10-16 6:53 ` [Bug c/111816] [gimple FE] ICE with _GIMPLE(ssa) and 2 returns rguenth at gcc dot gnu.org
2023-11-04 19:20 ` 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-111816-4-fdZ4qUeW6b@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).