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 target/103074] New: [11/12 Regression] ICE in lra_assign, at lra-assigns.c:1649
Date: Thu, 04 Nov 2021 04:03:09 +0000	[thread overview]
Message-ID: <bug-103074-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103074
           Summary: [11/12 Regression] ICE in lra_assign, at
                    lra-assigns.c:1649
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: x86_64-unknown-linux-gnu

gcc-12.0.0-alpha20211031 snapshot (g:ca84f39399fda80c770306465276ffd66d3766ed)
ICEs when compiling the following testcase, which could expose UB in run time,
w/ -march=bonnell -Os -fPIC -fschedule-insns:

void
serialize_collection (char *ptr, int a, int need_owner)
{
  if (need_owner)
    __builtin_sprintf(ptr, "%d:%d", 0, a);
  else
    {
      static char buff[32];

      __builtin_sprintf(buff, "%d:%d", a >> 32, a);
      __builtin_sprintf(ptr, "%d:%d:\"%s\"", 0, 0, buff);
    }
}

% x86_64-unknown-linux-gnu-gcc-12.0.0 -march=bonnell -Os -fPIC -fschedule-insns
-c jmolltrp.c
jmolltrp.c: In function 'serialize_collection':
jmolltrp.c:10:42: warning: right shift count >= width of type
[-Wshift-count-overflow]
   10 |       __builtin_sprintf(buff, "%d:%d", a >> 32, a);
      |                                          ^~
during RTL pass: reload
jmolltrp.c:13:1: internal compiler error: in lra_assign, at lra-assigns.c:1649
   13 | }
      | ^
0xce9af3 lra_assign(bool&)
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/lra-assigns.c:1649
0xce3da4 lra(_IO_FILE*)
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/lra.c:2387
0xc9c029 do_reload
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/ira.c:5932
0xc9c029 execute
       
/var/tmp/portage/sys-devel/gcc-12.0.0_alpha20211031/work/gcc-12-20211031/gcc/ira.c:6118

             reply	other threads:[~2021-11-04  4:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  4:03 asolokha at gmx dot com [this message]
2021-11-04  9:06 ` [Bug target/103074] [11/12 Regression] ICE in lra_assign, at lra-assigns.c:1649 since r11-5066-gbe39636d9f68c437 marxin at gcc dot gnu.org
2021-11-04  9:12 ` rguenth at gcc dot gnu.org
2021-11-22 18:07 ` jakub at gcc dot gnu.org
2021-11-22 18:18 ` jakub at gcc dot gnu.org
2021-11-23 10:48 ` ubizjak at gmail dot com
2022-03-10 21:17 ` cvs-commit at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2022-07-23  7:02 ` [Bug target/103074] [11 " asolokha at gmx dot com
2023-05-29 10:06 ` 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-103074-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).