public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109541] [12/13/14 regression] ICE in extract_constrain_insn on when building rhash-1.4.3 Date: Fri, 12 May 2023 10:06:57 +0000 [thread overview] Message-ID: <bug-109541-4-KuFRRls2a6@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 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org --- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- The problem is that LRA assigns a floating-point register to the PIC pseudo-register (pic_offset_table_rtx) and the SPARC back-end is not prepared for it. Vladimir, would it be feasible to prevent this from happening?
next prev parent reply other threads:[~2023-05-12 10:06 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-18 8:54 [Bug target/109541] New: ICE in extract_constrain_insn on sparc64-unknown-linux-gnu " 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 ` [Bug target/109541] [12 regression] " sjames at gcc dot gnu.org 2023-04-27 22:49 ` 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 [this message] 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-KuFRRls2a6@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).