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/107686] New: [12/13 Regression] ICE: verify_gimple failed (invalid types in nop conversion) with _Decimal64 vector Date: Mon, 14 Nov 2022 18:30:49 +0000 [thread overview] Message-ID: <bug-107686-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107686 Bug ID: 107686 Summary: [12/13 Regression] ICE: verify_gimple failed (invalid types in nop conversion) with _Decimal64 vector Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization 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 Compiler output: $ x86_64-pc-linux-gnu-gcc -O -mavx2 testcase.c testcase.c: In function 'foo': testcase.c:9:1: error: invalid types in nop conversion 9 | foo (void) | ^~~ _Decimal64 int _33 = (_Decimal64) _1; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _26 = (_Decimal64) _3; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _19 = (_Decimal64) _15; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _12 = (_Decimal64) _22; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _61 = (_Decimal64) _29; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _54 = (_Decimal64) _36; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _47 = (_Decimal64) _43; testcase.c:9:1: error: invalid types in nop conversion _Decimal64 int _40 = (_Decimal64) _50; during GIMPLE pass: forwprop testcase.c:9:1: internal compiler error: verify_gimple failed 0x142be1b verify_gimple_in_cfg(function*, bool, bool) /repo/gcc-trunk/gcc/tree-cfg.cc:5658 0x12d4590 execute_function_todo /repo/gcc-trunk/gcc/passes.cc:2091 0x12d4ace execute_todo /repo/gcc-trunk/gcc/passes.cc:2145 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-r13-4023-20221114155950-g2b85d759dae-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/13.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 --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-r13-4023-20221114155950-g2b85d759dae-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.0.0 20221114 (experimental) (GCC)
next reply other threads:[~2022-11-14 18:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-14 18:30 zsojka at seznam dot cz [this message] 2022-11-14 18:32 ` [Bug tree-optimization/107686] " zsojka at seznam dot cz 2022-11-14 18:41 ` pinskia at gcc dot gnu.org 2022-11-14 18:44 ` pinskia at gcc dot gnu.org 2022-11-16 13:15 ` rguenth at gcc dot gnu.org 2022-11-16 13:15 ` rguenth at gcc dot gnu.org 2022-11-16 16:08 ` cvs-commit at gcc dot gnu.org 2022-11-17 7:50 ` [Bug tree-optimization/107686] [12 " rguenth at gcc dot gnu.org 2022-12-12 11:20 ` cvs-commit at gcc dot gnu.org 2022-12-12 11:21 ` 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-107686-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).