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/111819] New: GCC: 14: internal compiler error: in fold_offsetof, at c-family/c-common.cc:6877
Date: Sun, 15 Oct 2023 01:44:46 +0000 [thread overview]
Message-ID: <bug-111819-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111819
Bug ID: 111819
Summary: GCC: 14: internal compiler error: in fold_offsetof, at
c-family/c-common.cc:6877
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: ---
The bug triggering program:
```
long long a;
void f(_Complex double x) {
(int *)&__imag(
*(_Complex double *)((char *)&a + 16));
}
```
This bug can be verified at: https://godbolt.org/z/6d98f8YT7
The full stack dump:
```
<source>: In function 'f':
<source>:4:7: internal compiler error: in fold_offsetof, at
c-family/c-common.cc:6877
4 | *(_Complex double *)((char *)&a + 16));
| ^
0x22ff3ee internal_error(char const*, ...)
???:0
0x9fc0a8 fancy_abort(char const*, int, char const*)
???:0
0xa4f1d8 build_unary_op(unsigned int, tree_code, tree_node*, bool)
???:0
0xa5c176 parser_build_unary_op(unsigned int, tree_code, c_expr)
???:0
0xaa468d c_parse_file()
???:0
0xb17919 c_common_parse_file()
???: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-15 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 1:44 141242068 at smail dot nju.edu.cn [this message]
2023-10-15 1:48 ` [Bug c/111819] " 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-111819-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).