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/111911] [11/12/13/14 Regression] ICE with integer overflow converting to _Bool
Date: Sun, 22 Oct 2023 02:28:51 +0000 [thread overview]
Message-ID: <bug-111911-4-rxmVZoG9hD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111911-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111911
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> I suspect it started with PR 93241 (and is very similar to PR 93348).
(_Bool) <<< Unknown tree: c_maybe_const_expr
1 >>> == 0)
So maybe remove_c_maybe_const_expr needs to be called always instead of just on
"argument with integer operands".
next prev parent reply other threads:[~2023-10-22 2:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 1:42 [Bug c/111911] New: GCC: 14: internal compiler error: internal compiler error: in gimplify_expr, at gimplify.cc:17510 141242068 at smail dot nju.edu.cn
2023-10-22 1:54 ` [Bug c/111911] [11/12/13/14 Regression] ICE with integer overflow converting to _Bool pinskia at gcc dot gnu.org
2023-10-22 1:54 ` pinskia at gcc dot gnu.org
2023-10-22 2:21 ` pinskia at gcc dot gnu.org
2023-10-22 2:25 ` pinskia at gcc dot gnu.org
2023-10-22 2:28 ` pinskia at gcc dot gnu.org [this message]
2023-11-22 14:38 ` jakub at gcc dot gnu.org
2024-01-30 22:16 ` jsm28 at gcc dot gnu.org
2024-01-31 1:25 ` cvs-commit at gcc dot gnu.org
2024-01-31 1:29 ` [Bug c/111911] [11/12/13 " jsm28 at gcc dot gnu.org
2024-02-08 1:35 ` cvs-commit 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-111911-4-rxmVZoG9hD@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).