public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103938] [9/10/11/12/13 Regression] ICE with __builtin_prefetch and vectors
Date: Thu, 28 Apr 2022 19:14:39 +0000	[thread overview]
Message-ID: <bug-103938-4-9NKORvh1e8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103938-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alex Coplan from comment #7)
> A bisect shows this started with
> r12-2288-g8695bf78dad1a42636775843ca832a2f4dba4da3 :
> 
> commit 8695bf78dad1a42636775843ca832a2f4dba4da3
> Author: Jonathan Wright <jonathan.wright@arm.com>
> Date:   Wed Jun 2 16:55:00 2021 +0100
> 
>     gcc: Add vec_select -> subreg RTL simplification
> 
> which makes it a [12/13 Regression], unless I'm missing something? Should it
> be a P1?

It only ices for checking and does not produce wrong code when release checking
so it would be a p2 in my mind.
Plus it was latent before that patch as I could reproduce on a gcc 10 (maybe I
have some other optimizations added which expose it in gcc 10).

  parent reply	other threads:[~2022-04-28 19:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 10:12 [Bug target/103938] New: " pinskia at gcc dot gnu.org
2022-01-07 10:51 ` [Bug target/103938] " pinskia at gcc dot gnu.org
2022-01-28  0:33 ` [Bug target/103938] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-28  0:35 ` pinskia at gcc dot gnu.org
2022-04-06 16:28 ` acoplan at gcc dot gnu.org
2022-04-06 16:36 ` pinskia at gcc dot gnu.org
2022-04-07  9:17 ` acoplan at gcc dot gnu.org
2022-04-19 15:30 ` rguenth at gcc dot gnu.org
2022-04-28 17:29 ` [Bug target/103938] [9/10/11/12/13 " acoplan at gcc dot gnu.org
2022-04-28 19:14 ` pinskia at gcc dot gnu.org [this message]
2022-05-27  9:47 ` [Bug target/103938] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug target/103938] [11/12/13/14 " 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-103938-4-9NKORvh1e8@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).