public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103938] [9/10/11/12 Regression] ICE with __builtin_prefetch and vectors
Date: Thu, 07 Apr 2022 09:17:48 +0000 [thread overview]
Message-ID: <bug-103938-4-dsAcOvC8DJ@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 #6 from Alex Coplan <acoplan at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Alex Coplan from comment #4)
> > Confirmed on trunk. I can only reproduce the ICE with trunk, not with
> > earlier released versions.
>
> Are you sure you configured the previous released versions with
> --enabled-checking=yes ? That is the only way to get the ICE on released
> versions.
Well, I just tried a clean build of the GCC 11 branch with
--enable-checking=yes, and I don't see the ICE there:
$ gcc/xgcc -B gcc -v
Reading specs from gcc/specs
COLLECT_GCC=gcc/xgcc
COLLECT_LTO_WRAPPER=gcc/lto-wrapper
Target: aarch64-linux-gnu
Configured with: /home/alecop01/toolchain/src/gcc/configure
--prefix=/data_sdb/toolchain/cc1s/gcc11-aarch64 --enable-languages=c,c++
--disable-bootstrap --target=aarch64-linux-gnu --enable-checking=yes
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.2.1 20220407 (GCC)
$ cat t.c
typedef unsigned long u64x2 __attribute__ ((vector_size(16)));
void g (u64x2 off)
{
__builtin_prefetch ((void*)off[0], 0, 3);
}
$ gcc/xgcc -B gcc -c t.c -O2
next prev parent reply other threads:[~2022-04-07 9:17 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 [this message]
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
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-dsAcOvC8DJ@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).