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/107244] New: error: invalid position or size in ‘bit_insert_expr’
Date: Thu, 13 Oct 2022 07:13:32 +0000	[thread overview]
Message-ID: <bug-107244-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107244

            Bug ID: 107244
           Summary: error: invalid position or size in ‘bit_insert_expr’
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 53699
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53699&action=edit
C source code

For the attached C code, recent gcc trunk does this:

$ /home/dcb/gcc/results/bin/gcc -c -w -O2 bug856.c 2>&1 | more
apply.c: In function ‘unleash_all’:
apply.c:582:1: error: invalid position or size in ‘bit_insert_expr’
_ifc__16 = BIT_INSERT_EXPR <_ifc__2, 0, 0xffffffffffffffffffffffffffffffab (1
bi
ts)>;
during GIMPLE pass: ifcvt
apply.c:582:1: internal compiler error: verify_gimple failed

             reply	other threads:[~2022-10-13  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  7:13 dcb314 at hotmail dot com [this message]
2022-10-13  7:20 ` [Bug tree-optimization/107244] " dcb314 at hotmail dot com
2022-10-13  7:42 ` [Bug tree-optimization/107244] [13 Regression] error: invalid position or size in ‘bit_insert_expr’ since r13-3219-g25413fdb2ac24933 marxin at gcc dot gnu.org
2022-10-13  7:42 ` marxin at gcc dot gnu.org
2022-10-13  7:43 ` marxin at gcc dot gnu.org
2022-10-14  7:27 ` 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-107244-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: link
Be 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).