public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113315] during GIMPLE pass: bitintlower0 ICE: in lower_mergeable_stmt, at gimple-lower-bitint.cc:2310 with _BitInt() used as array index Date: Wed, 10 Jan 2024 21:24:55 +0000 [thread overview] Message-ID: <bug-113315-4-pVrVe8lwtw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113315-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113315 --- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> --- Created attachment 57031 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57031&action=edit probably related testcase, ICEing elsewhere at -O0 Compiler output for testcase3.c: $ x86_64-pc-linux-gnu-gcc testcase3.c during GIMPLE pass: bitintlower0 testcase3.c: In function 'foo': testcase3.c:5:1: internal compiler error: in lower_stmt, at gimple-lower-bitint.cc:5421 5 | foo (void) | ^~~ 0xd7fc87 lower_stmt /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:5421 0x266bf59 gimple_lower_bitint /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:6514 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 prev parent reply other threads:[~2024-01-10 21:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 20:54 [Bug tree-optimization/113315] New: " zsojka at seznam dot cz 2024-01-10 21:06 ` [Bug tree-optimization/113315] " zsojka at seznam dot cz 2024-01-10 21:24 ` zsojka at seznam dot cz [this message] 2024-01-11 12:15 ` [Bug c/113315] " jakub at gcc dot gnu.org 2024-01-12 16:12 ` cvs-commit at gcc dot gnu.org 2024-01-12 16:14 ` jakub at gcc dot gnu.org 2024-01-20 17:08 ` 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-113315-4-pVrVe8lwtw@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).