public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107057] New: [10/11/12/13 Regression] ICE in extract_constrain_insn, at recog.cc:2692
Date: Tue, 27 Sep 2022 16:25:26 +0000	[thread overview]
Message-ID: <bug-107057-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107057
           Summary: [10/11/12/13 Regression] ICE in
                    extract_constrain_insn, at recog.cc:2692
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started between 20190630 and 20190728, at -O3 or -Ofast :


$ cat z1.c
typedef double v2df __attribute__ ((vector_size (16)));
v2df f (double a, double b)
{
  v2df v;
  double *c = (double *)&v;
  *c = a;
  *(c+1) = b;
  return v;
}
void g ()
{
  v2df x = f (1.0, 1.0);
  v2df y = f (2.0, 2.0);
  for (;*(double *)&x<=8; x+=y)
    g ();
}


$ gcc-13-20220925 -c z1.c -mavx -mcmodel=large -O2
$
$ gcc-13-20220925 -c z1.c -mavx -mcmodel=large -O3
z1.c: In function 'g':
z1.c:16:1: error: insn does not satisfy its constraints:
   16 | }
      | ^
(insn 76 407 101 5 (set (reg/v:V2DF 24 xmm4 [orig:108 x ] [108])
        (vec_concat:V2DF (mem/u/c:DF (reg:DI 0 ax [330]) [0  S8 A64])
            (mem/u/c:DF (reg:DI 4 si [331]) [0  S8 A64]))) "z1.c":7:10 5952
{vec_concatv2df}
     (expr_list:REG_EQUAL (const_vector:V2DF [
                (const_double:DF 1.0e+0 [0x0.8p+1]) repeated x2
            ])
        (nil)))
during RTL pass: reload
z1.c:16:1: internal compiler error: in extract_constrain_insn, at recog.cc:2692
0x69f5c0 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ../../gcc/rtl-error.cc:108
0x69f5e9 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ../../gcc/rtl-error.cc:118
0xe20add extract_constrain_insn(rtx_insn*)
        ../../gcc/recog.cc:2692
0xce0d77 check_rtl
        ../../gcc/lra.cc:2126
0xce6296 lra(_IO_FILE*)
        ../../gcc/lra.cc:2544
0xc93fc9 do_reload
        ../../gcc/ira.cc:5940
0xc93fc9 execute
        ../../gcc/ira.cc:6126

             reply	other threads:[~2022-09-27 16:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:25 gscfq@t-online.de [this message]
2022-09-27 16:30 ` [Bug target/107057] " pinskia at gcc dot gnu.org
2022-09-29  8:00 ` rguenth at gcc dot gnu.org
2022-09-29 11:41 ` marxin at gcc dot gnu.org
2022-09-29 12:52 ` ubizjak at gmail dot com
2022-09-29 15:01 ` [Bug rtl-optimization/107057] " ubizjak at gmail dot com
2022-10-19  6:28 ` crazylht at gmail dot com
2022-10-25  9:15 ` crazylht at gmail dot com
2022-10-26  2:16 ` crazylht at gmail dot com
2022-10-26  8:46 ` crazylht at gmail dot com
2022-10-26  8:47 ` crazylht at gmail dot com
2022-10-28  8:38 ` ubizjak at gmail dot com
2022-11-01  5:34 ` cvs-commit at gcc dot gnu.org
2022-11-01  5:38 ` crazylht at gmail dot com
2023-07-07 10:44 ` [Bug rtl-optimization/107057] [11/12 " rguenth at gcc dot gnu.org
2023-11-30 10:43 ` liuhongt 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-107057-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).