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/104511] New: [10/11/12 Regression] ICE: in emit_move_insn, at expr.cc:4010 with __builtin_convertvector() at -O Date: Sat, 12 Feb 2022 08:05:22 +0000 [thread overview] Message-ID: <bug-104511-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104511 Bug ID: 104511 Summary: [10/11/12 Regression] ICE: in emit_move_insn, at expr.cc:4010 with __builtin_convertvector() at -O Product: gcc Version: 12.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: powerpc64le-unknown-linux-gnu Created attachment 52425 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52425&action=edit reduced testcase Compiler output: $ powerpc64le-unknown-linux-gnu-gcc -O testcase.c -Wno-psabi during RTL pass: expand testcase.c: In function 'foo': testcase.c:9:5: internal compiler error: in emit_move_insn, at expr.cc:4010 9 | D d = __builtin_convertvector (f, D); | ^ 0x64498b emit_move_insn(rtx_def*, rtx_def*) /repo/gcc-trunk/gcc/expr.cc:4010 0xa9421a expand_gimple_stmt_1 /repo/gcc-trunk/gcc/cfgexpand.cc:3994 0xa9421a expand_gimple_stmt /repo/gcc-trunk/gcc/cfgexpand.cc:4028 0xa99da8 expand_gimple_basic_block /repo/gcc-trunk/gcc/cfgexpand.cc:6069 0xa9c0b7 execute /repo/gcc-trunk/gcc/cfgexpand.cc:6795 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. $ powerpc64le-unknown-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-powerpc64le/bin/powerpc64le-unknown-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-7195-20220211112825-g72f8d228aff-checking-yes-rtl-df-extra-powerpc64le/bin/../libexec/gcc/powerpc64le-unknown-linux-gnu/12.0.1/lto-wrapper Target: powerpc64le-unknown-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --with-sysroot=/usr/powerpc64le-unknown-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=powerpc64le-unknown-linux-gnu --with-ld=/usr/bin/powerpc64le-unknown-linux-gnu-ld --with-as=/usr/bin/powerpc64le-unknown-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r12-7195-20220211112825-g72f8d228aff-checking-yes-rtl-df-extra-powerpc64le Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.0.1 20220211 (experimental) (GCC)
next reply other threads:[~2022-02-12 8:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-12 8:05 zsojka at seznam dot cz [this message] 2022-02-14 8:53 ` [Bug target/104511] " rguenth at gcc dot gnu.org 2022-02-14 10:26 ` cvs-commit at gcc dot gnu.org 2022-02-14 10:26 ` [Bug target/104511] [10/11 " rguenth at gcc dot gnu.org 2022-03-16 8:22 ` cvs-commit at gcc dot gnu.org 2022-03-16 9:22 ` [Bug target/104511] [10 " cvs-commit at gcc dot gnu.org 2022-03-16 9:24 ` 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-104511-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).