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 middle-end/114913] "verify_gimple failed" due to addition of two constexpr strings
Date: Wed, 01 May 2024 23:00:30 +0000 [thread overview]
Message-ID: <bug-114913-4-6E6meiqo8z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114913
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jorg Brown from comment #4)
> Also odd is that the above code (including a()) works fine on gcc 10.1
> through 13.2. As seen https://godbolt.org/z/z3qnosG37
This is not really odd since it does fail with those compilers with -fchecking
(which is the default for the GCC trunk development). It also works with the
trunk (in this case) with -fno-checking . Basically GCC has some internal
checks to make sure things internally are consistent but they are failing in
this case and you can turn them off/on at compile time.
next prev parent reply other threads:[~2024-05-01 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 21:02 [Bug c++/114913] New: " jorg.brown at gmail dot com
2024-05-01 21:11 ` [Bug middle-end/114913] " pinskia at gcc dot gnu.org
2024-05-01 21:18 ` mpolacek at gcc dot gnu.org
2024-05-01 22:24 ` pinskia at gcc dot gnu.org
2024-05-01 22:29 ` pinskia at gcc dot gnu.org
2024-05-01 22:55 ` jorg.brown at gmail dot com
2024-05-01 23:00 ` pinskia at gcc dot gnu.org [this message]
2024-05-02 11:28 ` [Bug c++/114913] " rguenth at gcc dot gnu.org
2024-05-02 14:13 ` ppalka at gcc dot gnu.org
2024-05-02 15:21 ` ppalka 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-114913-4-6E6meiqo8z@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).