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/111855] New: GCC: 14: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:265
Date: Wed, 18 Oct 2023 03:18:13 +0000 [thread overview]
Message-ID: <bug-111855-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111855
Bug ID: 111855
Summary: GCC: 14: internal compiler error: tree check: expected
class 'type', have 'exceptional' (error_mark) in
useless_type_conversion_p, at gimple-expr.cc:265
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 with GCC-14, gcc throws internal compiler error:
```
extern void *memmove(void [3], const void *, __SIZE_TYPE__);
void f(void)
{
char s[] = "12345";
memmove(s + 1, s, 4);
}
```
Compiler Explorer: https://gcc.godbolt.org/z/5zcnehhzo
The full stack:
```
<source>:1:27: error: declaration of type name as array of voids
1 | extern void *memmove(void [3], const void *, __SIZE_TYPE__);
| ^
<source>: In function 'f':
<source>:6:12: error: type of formal parameter 1 is incomplete
6 | memmove(s + 1, s, 4);
| ~~^~~
<source>:6:2: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:265
6 | memmove(s + 1, s, 4);
| ^~~~~~~
0x230ff8e internal_error(char const*, ...)
???:0
0x8a8944 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
???:0
0xdb9a31 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdb9247 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbc21a gimplify_stmt(tree_node**, gimple**)
???:0
0xdba1c3 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbc21a gimplify_stmt(tree_node**, gimple**)
???:0
0xdb926f gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
???:0
0xdbc21a gimplify_stmt(tree_node**, gimple**)
???:0
0xdbe233 gimplify_body(tree_node*, bool)
???:0
0xdbe68f gimplify_function_tree(tree_node*)
???:0
0xbe7db7 cgraph_node::analyze()
???:0
0xbeb901 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-18 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 3:18 141242068 at smail dot nju.edu.cn [this message]
2023-10-18 3:23 ` [Bug c/111855] " pinskia at gcc dot gnu.org
2023-10-18 3:25 ` 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-111855-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).