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/115642] New: [gcc][trunk] internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in c_expr_sizeof_expr Date: Tue, 25 Jun 2024 12:31:19 +0000 [thread overview] Message-ID: <bug-115642-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115642 Bug ID: 115642 Summary: [gcc][trunk] internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in c_expr_sizeof_expr Product: gcc Version: 15.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: --- Compiler explorer: https://gcc.godbolt.org/z/EWcfsT9hW This crash involve gcc-trunk, no additional options are required. The crash triggering program: ``` void f (int N) { int a[2][N]; sizeof ((int [2][N])a); } ``` The stack dump: ``` <source>:3:3: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in c_expr_sizeof_expr, at c/c-typeck.cc:3390 3 | sizeof ((int [2][N])a); | ^~~~~~ 0x23be10c internal_error(char const*, ...) ???:0 0x8948df tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) ???:0 0xa3bf1b c_parse_file() ???:0 0xab5959 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:[~2024-06-25 12:31 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-25 12:31 141242068 at smail dot nju.edu.cn [this message] 2024-06-25 18:39 ` [Bug c/115642] [11/12/13/14/15 Regression] " mpolacek 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-115642-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: linkBe 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).