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 target/112359] New: [14 Regression] ICE: in expand_fn_using_insn, at internal-fn.cc:215 with -O -ftree-loop-if-convert -mavx512fp16 Date: Fri, 03 Nov 2023 06:00:17 +0000 [thread overview] Message-ID: <bug-112359-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112359 Bug ID: 112359 Summary: [14 Regression] ICE: in expand_fn_using_insn, at internal-fn.cc:215 with -O -ftree-loop-if-convert -mavx512fp16 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 56498 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56498&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -O -ftree-loop-if-convert -mavx512fp16 testcase.c during RTL pass: expand testcase.c: In function 'foo': testcase.c:5:1: internal compiler error: in expand_fn_using_insn, at internal-fn.cc:215 5 | foo (void) | ^~~ 0x788f3f expand_fn_using_insn /repo/gcc-trunk/gcc/internal-fn.cc:215 0xf4bbcf expand_call_stmt /repo/gcc-trunk/gcc/cfgexpand.cc:2737 0xf4bbcf expand_gimple_stmt_1 /repo/gcc-trunk/gcc/cfgexpand.cc:3880 0xf4bbcf expand_gimple_stmt /repo/gcc-trunk/gcc/cfgexpand.cc:4044 0xf5218e expand_gimple_basic_block /repo/gcc-trunk/gcc/cfgexpand.cc:6100 0xf53e67 execute /repo/gcc-trunk/gcc/cfgexpand.cc:6835 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. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r14-5093-20231103113523-gc3847ca0571-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r14-5093-20231103113523-gc3847ca0571-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20231103 (experimental) (GCC)
next reply other threads:[~2023-11-03 6:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-03 6:00 zsojka at seznam dot cz [this message] 2023-11-03 8:11 ` [Bug target/112359] " rguenth at gcc dot gnu.org 2023-11-06 12:03 ` [Bug middle-end/112359] " rdapp at gcc dot gnu.org 2023-11-06 12:35 ` rguenther at suse dot de 2023-11-07 21:38 ` cvs-commit at gcc dot gnu.org 2023-11-08 6:59 ` rguenth 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-112359-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).