public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109541] [12 regression] ICE in extract_constrain_insn on sparc64-unknown-linux-gnu when building rhash-1.4.3
Date: Thu, 27 Apr 2023 22:49:13 +0000 [thread overview]
Message-ID: <bug-109541-4-gh05vgblAe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109541-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109541
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE in |[12 regression] ICE in
|extract_constrain_insn on |extract_constrain_insn on
|sparc64-unknown-linux-gnu |sparc64-unknown-linux-gnu
|when building rhash-1.4.3 |when building rhash-1.4.3
--- Comment #2 from Sam James <sjames at gcc dot gnu.org> ---
With < 12, need -ftree-vectorize because the default changed. I can repro w/
10/11/12/13.
It's not very easy for me to bisect older versions because they don't e.g.
build with newer glibc and I always lose track of the patch(es) for those kind
of problems. But I'm pretty suspicious of this being a dupe still, so I guess
it's not so important.
next prev parent reply other threads:[~2023-04-27 22:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:54 [Bug target/109541] New: " sjames at gcc dot gnu.org
2023-04-18 8:54 ` [Bug target/109541] " sjames at gcc dot gnu.org
2023-04-27 22:49 ` sjames at gcc dot gnu.org [this message]
2023-04-27 22:49 ` [Bug target/109541] [12 regression] " sjames at gcc dot gnu.org
2023-04-27 22:50 ` sjames at gcc dot gnu.org
2023-05-02 6:50 ` [Bug target/109541] [12/13/14 " rguenth at gcc dot gnu.org
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2023-05-12 8:03 ` [Bug target/109541] [12/13/14 regression] ICE in extract_constrain_insn on " ebotcazou at gcc dot gnu.org
2023-05-12 10:06 ` ebotcazou at gcc dot gnu.org
2023-05-12 10:07 ` ebotcazou at gcc dot gnu.org
2023-05-12 13:40 ` vmakarov at gcc dot gnu.org
2023-05-31 21:00 ` vmakarov at gcc dot gnu.org
2023-05-31 21:57 ` ebotcazou at gcc dot gnu.org
2023-05-31 21:58 ` ebotcazou at gcc dot gnu.org
2023-05-31 22:24 ` sjames at gcc dot gnu.org
2023-06-04 1:55 ` sjames at gcc dot gnu.org
2023-06-04 7:12 ` ebotcazou at gcc dot gnu.org
2023-06-04 7:24 ` sjames at gcc dot gnu.org
2023-06-05 19:57 ` vmakarov at gcc dot gnu.org
2023-06-06 4:12 ` sjames at gcc dot gnu.org
2023-06-07 15:35 ` cvs-commit at gcc dot gnu.org
2023-06-07 15:50 ` ebotcazou at gcc dot gnu.org
2023-06-16 19:52 ` [Bug target/109541] [12/13 " cvs-commit at gcc dot gnu.org
2023-06-20 8:08 ` [Bug target/109541] [12 " 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-109541-4-gh05vgblAe@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).