public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/111441] [14 Regression] ICE generating access diagram, in fold_binary_loc, at fold-const.cc:11580
Date: Wed, 14 Feb 2024 14:40:32 +0000 [thread overview]
Message-ID: <bug-111441-4-HfKkAaMfuD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111441-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111441
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|internal compiler error: in |[14 Regression] ICE
|fold_binary_loc, at |generating access diagram,
|fold-const.cc:11580 |in fold_binary_loc, at
| |fold-const.cc:11580
Ever confirmed|0 |1
Last reconfirmed| |2024-02-14
Status|UNCONFIRMED |NEW
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this. Still affects trunk, though I had to add a "void" to
the return type of f to avoid <source>:2:1: error: return type defaults to
'int' [-Wimplicit-int]:
https://godbolt.org/z/WM8zbvrxf
next prev parent reply other threads:[~2024-02-14 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 8:44 [Bug analyzer/111441] New: internal compiler error: " dale.mengli.ming at proton dot me
2023-09-17 9:07 ` [Bug analyzer/111441] " pinskia at gcc dot gnu.org
2023-09-17 9:16 ` dale.mengli.ming at proton dot me
2023-09-17 9:19 ` dale.mengli.ming at proton dot me
2023-10-25 8:27 ` dale.mengli.ming at proton dot me
2024-02-14 14:40 ` dmalcolm at gcc dot gnu.org [this message]
2024-03-04 13:01 ` [Bug analyzer/111441] [14 Regression] ICE generating access diagram, " rguenth at gcc dot gnu.org
2024-03-07 22:29 ` law at gcc dot gnu.org
2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
2024-03-18 22:52 ` dmalcolm 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-111441-4-HfKkAaMfuD@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).