public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "141242068 at smail dot nju.edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111911] New: GCC: 14: internal compiler error: internal compiler error: in gimplify_expr, at gimplify.cc:17510
Date: Sun, 22 Oct 2023 01:42:44 +0000 [thread overview]
Message-ID: <bug-111911-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111911
Bug ID: 111911
Summary: GCC: 14: internal compiler error: internal compiler
error: in gimplify_expr, at gimplify.cc:17510
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: 141242068 at smail dot nju.edu.cn
Target Milestone: ---
When compile this program, GCC crashes:
```
int main(void) {
if ((((!((_Bool)(__INT_MAX__ + 1))) /
(!((_Bool)(__INT_MAX__ + 1))))))
;
return 1;
}
```
Complier Explorer: https://gcc.godbolt.org/z/W59roeYKP
The full stack dump:
```
<source>: In function 'main':
<source>:2:32: warning: integer overflow in expression of type 'int' results in
'-2147483648' [-Woverflow]
2 | if ((((!((_Bool)(__INT_MAX__ + 1))) /
| ^
<source>:3:34: warning: integer overflow in expression of type 'int' results in
'-2147483648' [-Woverflow]
3 | (!((_Bool)(__INT_MAX__ + 1))))))
| ^
cc1: warning: division by zero [-Wdiv-by-zero]
<source>:2:10: internal compiler error: in gimplify_expr, at gimplify.cc:17510
2 | if ((((!((_Bool)(__INT_MAX__ + 1))) /
| ^
0x231f49e internal_error(char const*, ...)
???:0
0xa00958 fancy_abort(char const*, int, char const*)
???:0
0xdbb856 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbb3dc gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbb856 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbb3dc gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbb3dc gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbbf48 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbec8a gimplify_stmt(tree_node**, gimple**)
???:0
0xdbcc33 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbec8a gimplify_stmt(tree_node**, gimple**)
???:0
0xdbbcdf gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbec8a gimplify_stmt(tree_node**, gimple**)
???:0
0xdbcc33 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbec8a gimplify_stmt(tree_node**, gimple**)
???:0
0xdc0cd3 gimplify_body(tree_node*, bool)
???:0
0xdc112f gimplify_function_tree(tree_node*)
???:0
0xbea6e7 cgraph_node::analyze()
???:0
0xbee231 symbol_table::finalize_compilation_unit()
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
```
next reply other threads:[~2023-10-22 1:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 1:42 141242068 at smail dot nju.edu.cn [this message]
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
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@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).