public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105573] ICE when building numpy on SPARC64
Date: Wed, 11 May 2022 22:03:14 +0000 [thread overview]
Message-ID: <bug-105573-4-UpjVgMbFMz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105573-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105573
--- Comment #1 from Sam James <sam at gentoo dot org> ---
It occurs with -mcpu=native or -mcpu=niagara4 but not if I drop that.
```
$ for t in param target; do cmd="gcc -Q -O2 --help=$t"; diff -U0 <(LANG=C $cmd)
<(LANG=C $cmd -mcpu=niagara4); done
--- /dev/fd/63 2022-05-11 15:01:56.915134318 -0700
+++ /dev/fd/62 2022-05-11 15:01:56.915134318 -0700
@@ -85,2 +85,2 @@
- --param=l1-cache-size= 64
- --param=l2-cache-size= 512
+ --param=l1-cache-size= 16
+ --param=l2-cache-size= 128
@@ -223 +223 @@
- --param=simultaneous-prefetches= 3
+ --param=simultaneous-prefetches= 2
--- /dev/fd/63 2022-05-11 15:01:56.965136466 -0700
+++ /dev/fd/62 2022-05-11 15:01:56.975136897 -0700
@@ -6 +6 @@
- -mcbcond [disabled]
+ -mcbcond [enabled]
@@ -8 +8 @@
- -mcpu= v9
+ -mcpu= niagara4
@@ -16 +16 @@
- -mfmaf [disabled]
+ -mfmaf [enabled]
@@ -27 +27 @@
- -mpopc [disabled]
+ -mpopc [enabled]
@@ -36 +36 @@
- -mtune= v9
+ -mtune= niagara4
@@ -41,3 +41,3 @@
- -mvis [disabled]
- -mvis2 [disabled]
- -mvis3 [disabled]
+ -mvis [enabled]
+ -mvis2 [enabled]
+ -mvis3 [enabled]
```
It looks like -mvis3 is the trigger:
```
$ sparc64-unknown-linux-gnu-gcc -O2 -pipe -c loops.i -mvis3
[...]
during GIMPLE pass: isel
loops.i:3:33: internal compiler error: in gimple_expand_vec_cond_expr, at
gimple-isel.cc:267
3 | __attribute__((optimize("O3"))) UINT_sign() {
| ^~~~~~~~~
0x5c4b2f internal_error(char const*, ...)
???:0
0x5bc583 fancy_abort(char const*, int, char const*)
???:0
[...]
```
next prev parent reply other threads:[~2022-05-11 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 21:57 [Bug c++/105573] New: " sam at gentoo dot org
2022-05-11 22:03 ` sam at gentoo dot org [this message]
2022-05-11 22:16 ` [Bug target/105573] " mpolacek at gcc dot gnu.org
2022-05-11 22:19 ` pinskia at gcc dot gnu.org
2022-05-11 22:46 ` sam at gentoo dot org
2022-05-11 22:52 ` pinskia at gcc dot gnu.org
2022-05-12 11:34 ` rguenth at gcc dot gnu.org
2022-05-12 15:36 ` sam at gentoo dot org
2022-05-19 14:06 ` rguenth at gcc dot gnu.org
2023-04-25 6:21 ` cvs-commit 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-105573-4-UpjVgMbFMz@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).