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/106433] [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032
Date: Wed, 26 Oct 2022 16:39:17 +0000	[thread overview]
Message-ID: <bug-106433-4-pHfWBvwDFQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106433-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
JFTR, I believe I can reproduce the same issue on x86_64 w/ the current gcc
13.0.0 20221023 (g:0e37fd4dc74c1db99cdc7d71ef378e1221253c6f) snapshot:

int m;
int *p;

__attribute__ ((simd)) int
bar (int x)
{
  if (x)
    {
      if (m < 1)
        for (m = 0; m < 1; ++m)
          ++x;

      p = &x;

      for (;;)
        ++m;
    }

  return 0;
}

__attribute__ ((simd)) int
foo (int x)
{
  return bar (x);
}

% x86_64-unknown-linux-gnu-gcc-13 -O2 -c rf5yfvga.c
during GIMPLE pass: vect
rf5yfvga.c: In function 'foo.simdclone.0':
rf5yfvga.c:23:1: internal compiler error: in vect_transform_loops, at
tree-vectorizer.cc:1032
   23 | foo (int x)
      | ^~~
0x7ac573 vect_transform_loops
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-vectorizer.cc:1032
0x11dd81f try_vectorize_loop_1
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-vectorizer.cc:1153
0x11dd81f try_vectorize_loop
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-vectorizer.cc:1183
0x11ddbd4 execute
       
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221023/work/gcc-13-20221023/gcc/tree-vectorizer.cc:1299

  parent reply	other threads:[~2022-10-26 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  8:12 [Bug tree-optimization/106433] New: " asolokha at gmx dot com
2022-07-25  9:46 ` [Bug tree-optimization/106433] " rguenth at gcc dot gnu.org
2022-10-19 10:43 ` rguenth at gcc dot gnu.org
2022-10-26 16:39 ` asolokha at gmx dot com [this message]
2022-12-12 11:19 ` rguenth at gcc dot gnu.org
2023-02-06 11:55 ` jakub at gcc dot gnu.org
2023-02-07  9:34 ` cvs-commit at gcc dot gnu.org
2023-02-07  9:41 ` 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-106433-4-pHfWBvwDFQ@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).