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/94438] New: [8/9/10 Regression] ICE: verify_gimple failed: position plus size exceeds size of referenced object in 'bit_field_ref' with -mavx512vbmi -mavx512vl Date: Wed, 01 Apr 2020 10:47:28 +0000 [thread overview] Message-ID: <bug-94438-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94438 Bug ID: 94438 Summary: [8/9/10 Regression] ICE: verify_gimple failed: position plus size exceeds size of referenced object in 'bit_field_ref' with -mavx512vbmi -mavx512vl Product: gcc Version: 10.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 Created attachment 48161 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48161&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -mavx512vbmi -mavx512vl testcase.c testcase.c: In function 'foo': testcase.c:4:1: error: position plus size exceeds size of referenced object in 'bit_field_ref' 4 | foo (void) | ^~~ _8 = BIT_FIELD_REF <_7, 128, 0>; during GIMPLE pass: veclower testcase.c:4:1: internal compiler error: verify_gimple failed 0x102b7aa verify_gimple_in_cfg(function*, bool) /repo/gcc-trunk/gcc/tree-cfg.c:5459 0xeed15f execute_function_todo /repo/gcc-trunk/gcc/passes.c:1985 0xeedfac do_per_function /repo/gcc-trunk/gcc/passes.c:1640 0xeedfac execute_todo /repo/gcc-trunk/gcc/passes.c:2039 Please submit a full bug report, with preprocessed source if appropriate. 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/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r10-7475-20200331110822-g1ef979c6966-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/10.0.1/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-r10-7475-20200331110822-g1ef979c6966-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.0.1 20200331 (experimental) (GCC)
next reply other threads:[~2020-04-01 10:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-01 10:47 zsojka at seznam dot cz [this message] 2020-04-01 11:12 ` [Bug target/94438] " jakub at gcc dot gnu.org 2020-04-01 11:18 ` jakub at gcc dot gnu.org 2020-04-02 15:24 ` jakub at gcc dot gnu.org 2020-04-08 16:25 ` cvs-commit at gcc dot gnu.org 2020-04-08 16:26 ` [Bug target/94438] [8/9 " jakub at gcc dot gnu.org 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:25 ` jakub 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-94438-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).