public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98655] New: ICE: verify_gimple failed (error: integral result type precision does not match field size of 'bit_field_ref') Date: Wed, 13 Jan 2021 07:08:13 +0000 [thread overview] Message-ID: <bug-98655-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98655 Bug ID: 98655 Summary: ICE: verify_gimple failed (error: integral result type precision does not match field size of 'bit_field_ref') Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: powerpc-*-linux-gnu gcc-11.0.0-alpha20210110 snapshot (g:872373360dab259d51caa002ff1722ff84746d8b) configured for rs6000 target ICEs when compiling the following testcase, reduced from testsuite/gcc.target/i386/pr97521.c, w/ -O1 -fno-tree-forwprop: typedef unsigned char __attribute__ ((__vector_size__ (8))) V; typedef unsigned long long __attribute__ ((__vector_size__ (16))) W; V foo (W f) { W g = ((W) { 0, 1 } < 1) <= (0 < f); return (V) (g[0]); } % powerpc-e300c3-linux-gnu-gcc-11.0.0 -O1 -fno-tree-forwprop -w -c mvzpqney.c mvzpqney.c: In function 'foo': mvzpqney.c:5:1: error: integral result type precision does not match field size of 'bit_field_ref' 5 | foo (W f) | ^~~ _10 = BIT_FIELD_REF <_9, 1, 0>; mvzpqney.c:5:1: error: integral result type precision does not match field size of 'bit_field_ref' _12 = BIT_FIELD_REF <_11, 1, 0>; mvzpqney.c:5:1: error: integral result type precision does not match field size of 'bit_field_ref' _16 = BIT_FIELD_REF <_15, 1, 1>; mvzpqney.c:5:1: error: integral result type precision does not match field size of 'bit_field_ref' _18 = BIT_FIELD_REF <_17, 1, 1>; during GIMPLE pass: veclower2 mvzpqney.c:5:1: internal compiler error: verify_gimple failed 0xe59f67 verify_gimple_in_cfg(function*, bool) /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210110/work/gcc-11-20210110/gcc/tree-cfg.c:5467 0xd27b0e execute_function_todo /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210110/work/gcc-11-20210110/gcc/passes.c:2042 0xd2821c do_per_function /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210110/work/gcc-11-20210110/gcc/passes.c:1687 0xd2821c execute_todo /var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20210110/work/gcc-11-20210110/gcc/passes.c:2096
next reply other threads:[~2021-01-13 7:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-13 7:08 asolokha at gmx dot com [this message] 2021-01-13 8:19 ` [Bug tree-optimization/98655] " rguenth at gcc dot gnu.org 2021-01-13 10:47 ` asolokha at gmx dot com 2021-03-22 9:14 ` asolokha at gmx dot com 2021-03-22 9:19 ` marxin 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-98655-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).