public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105292] [sparc64] ICE in expand_expr_real_2 on sparc64 when compiling with -mcpu=niagara4 Date: Wed, 20 Apr 2022 16:26:57 +0000 [thread overview] Message-ID: <bug-105292-4-KVbifJdTLF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105292-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105292 --- Comment #2 from Mikael Pettersson <mikpelinux at gmail dot com> --- Works with gcc-9.4, ICEs with gcc-10.3 and above. Git bisect identified # first bad commit: [9b75f56d4b7951c60a656396dddd4a65787b95bc] Apply maximum nunits for BB SLP as the cause of the ICEs, though it possibly only exposed a latent target issue.
next prev parent reply other threads:[~2022-04-20 16:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 14:28 [Bug c/105292] New: " koachan+gccbugs at protonmail dot com 2022-04-18 9:59 ` [Bug target/105292] " mikpelinux at gmail dot com 2022-04-20 16:26 ` mikpelinux at gmail dot com [this message] 2022-05-06 7:58 ` [Bug target/105292] [10/11/12/13 regression] ICE in expand_expr_real_2 when compiling with -mcpu=niagara4 -mvis2 ebotcazou at gcc dot gnu.org 2022-05-06 8:21 ` ebotcazou at gcc dot gnu.org 2022-05-06 9:47 ` ebotcazou at gcc dot gnu.org 2022-05-10 7:36 ` [Bug target/105292] [10/11/12/13 regression] ICE in expand_expr_real_2 when compiling with -mvis2 cvs-commit at gcc dot gnu.org 2022-05-10 7:41 ` cvs-commit at gcc dot gnu.org 2022-05-10 7:45 ` cvs-commit at gcc dot gnu.org 2022-05-10 7:47 ` cvs-commit at gcc dot gnu.org 2022-05-10 7:48 ` cvs-commit at gcc dot gnu.org 2022-05-10 7:50 ` ebotcazou at gcc dot gnu.org 2022-06-03 11:02 ` ebotcazou 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-105292-4-KVbifJdTLF@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: linkBe 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).