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/110682] New: GCC, ICE: internal compiler error: in gimplify_expr, at gimplify.cc:16771
Date: Sun, 16 Jul 2023 10:57:27 +0000	[thread overview]
Message-ID: <bug-110682-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110682

            Bug ID: 110682
           Summary: GCC, ICE: internal compiler error: in gimplify_expr,
                    at gimplify.cc:16771
           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 compiling below program using gcc-14 with option `gcc-14 -Ofast a.c`,
gcc-14 crashes:
```
struct a {
  const signed char b;
};

void f(volatile struct a *c) {
  c - 0 % c->b;
  struct a c = {1};
}
```

GCC's output is pasted below:
```
<source>: In function 'f':
<source>:7:12: error: 'c' redeclared as different kind of symbol
    7 |   struct a c = {1};
      |            ^
<source>:5:27: note: previous definition of 'c' with type 'volatile struct a *'
    5 | void f(volatile struct a *c) {
      |        ~~~~~~~~~~~~~~~~~~~^
<source>:6:5: internal compiler error: in gimplify_expr, at gimplify.cc:16771
    6 |   c - 0 % c->b;
      |   ~~^~~~~~~~~~
0x2150dee internal_error(char const*, ...)
        ???:0
0x9ce06c fancy_abort(char const*, int, char const*)
        ???:0
0xd7057a gimplify_stmt(tree_node**, gimple**)
        ???:0
0xd6d9ba gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ???:0
0xd7057a gimplify_stmt(tree_node**, gimple**)
        ???:0
0xd6e4eb gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ???:0
0xd7057a gimplify_stmt(tree_node**, gimple**)
        ???:0
0xd6d954 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
        ???:0
0xd7057a gimplify_stmt(tree_node**, gimple**)
        ???:0
0xd71a13 gimplify_body(tree_node*, bool)
        ???:0
0xd71e6f gimplify_function_tree(tree_node*)
        ???:0
0xbaebe7 cgraph_node::analyze()
        ???:0
0xbb2731 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.
```

This can be verified by visiting the Compiler Explorer:
https://gcc.godbolt.org/z/5951jvono

             reply	other threads:[~2023-07-16 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 10:57 141242068 at smail dot nju.edu.cn [this message]
2023-11-13 19:17 ` [Bug c/110682] [12/13/14 Regression] ICE: internal compiler error: in gimplify_expr after error pinskia at gcc dot gnu.org
2023-12-05 22:58 ` pinskia at gcc dot gnu.org
2024-03-07 23:29 ` law at gcc dot gnu.org
2024-03-07 23:31 ` pinskia at gcc dot gnu.org
2024-03-08  3:43 ` pinskia at gcc dot gnu.org
2024-03-12 13:24 ` jakub at gcc dot gnu.org
2024-03-23  5:51 ` 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-110682-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).