public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108688] New: error: ‘bit_field_ref’ of non-mode-precision operand Date: Mon, 06 Feb 2023 19:50:32 +0000 [thread overview] Message-ID: <bug-108688-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108688 Bug ID: 108688 Summary: error: ‘bit_field_ref’ of non-mode-precision operand Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this C code: union { signed f1 : 7; signed f2 : 2 } func_6_l_2225; g_139, g_417, func_6___trans_tmp_7; main() { for (; g_417; g_417 -= 1) { func_6_l_2225.f1 = g_139; func_6_l_2225.f2 ^= func_6___trans_tmp_7; } } Compiled by recent gcc, does this: $ ~/gcc/results/bin/gcc -c -O2 -w bug882.c bug882.c: In function ‘main’: bug882.c:6:1: error: ‘bit_field_ref’ of non-mode-precision operand 6 | main() { | ^~~~ _ifc__31 = BIT_FIELD_REF <_2, 2, 0>; during GIMPLE pass: ifcvt bug882.c:6:1: internal compiler error: verify_gimple failed $ ~/gcc/results/bin/gcc -v 2>&1 | fgrep exp gcc version 13.0.1 20230206 (experimental) (45e01229af33a3dc) $ The bug first seems to occur sometime between date 20221002 and 20221028.
next reply other threads:[~2023-02-06 19:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-06 19:50 dcb314 at hotmail dot com [this message] 2023-02-06 19:52 ` [Bug tree-optimization/108688] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-06 19:54 ` pinskia at gcc dot gnu.org 2023-02-06 20:16 ` pinskia at gcc dot gnu.org 2023-02-07 14:07 ` rguenth at gcc dot gnu.org 2023-02-08 11:49 ` jakub at gcc dot gnu.org 2023-02-08 12:15 ` jakub at gcc dot gnu.org 2023-02-08 12:18 ` pinskia at gcc dot gnu.org 2023-02-08 12:41 ` jakub at gcc dot gnu.org 2023-02-08 16:26 ` pinskia at gcc dot gnu.org 2023-02-08 16:40 ` pinskia at gcc dot gnu.org 2023-02-08 21:15 ` pinskia at gcc dot gnu.org 2023-02-09 15:07 ` cvs-commit at gcc dot gnu.org 2023-02-09 15:11 ` cvs-commit at gcc dot gnu.org 2023-02-09 15:15 ` jakub at gcc dot gnu.org 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:21 ` cvs-commit 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-108688-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).