public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111497] New: [11/12/13/14 Regression] ICE building mariadb on i686 since r8-470 Date: Wed, 20 Sep 2023 14:35:07 +0000 [thread overview] Message-ID: <bug-111497-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111497 Bug ID: 111497 Summary: [11/12/13/14 Regression] ICE building mariadb on i686 since r8-470 Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- The following testcase ICEs on x86_64-linux with -m32 -march=i686 -mtune=generic -fPIC -O2 -g starting with r8-470-g973dfbb4a63ba7c580e4 The error is: during RTL pass: pro_and_epilogue item.ii: In constructor ‘G::G(A*, const B&, const B&, const B&)’: item.ii:19:1: internal compiler error: in find_oldest_value_reg, at regcprop.cc:465 19 | } | ^ 0x10304d0 find_oldest_value_reg ../../gcc/regcprop.cc:465 0x10307eb replace_oldest_value_reg ../../gcc/regcprop.cc:512 0x1030fe0 replace_oldest_value_addr ../../gcc/regcprop.cc:671 0x10311c3 replace_oldest_value_mem ../../gcc/regcprop.cc:704 and it is apparently due to LRA leaving a reference to a pseudo register in a DEBUG_INSN: (debug_insn 28 27 29 2 (var_location:SI x (mem/f:SI (reg:SI 110) [1 *y_10(D).b1+0 S4 A32])) "item.ii":4:39 -1 (nil)) in *.reload dump and forward. Vlad, could you please have a look?
next reply other threads:[~2023-09-20 14:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-20 14:35 jakub at gcc dot gnu.org [this message] 2023-09-20 14:35 ` [Bug middle-end/111497] " jakub at gcc dot gnu.org 2023-09-20 14:36 ` jakub at gcc dot gnu.org 2023-09-20 14:41 ` jakub at gcc dot gnu.org 2023-09-20 14:55 ` jakub at gcc dot gnu.org 2023-09-22 19:50 ` vmakarov at gcc dot gnu.org 2023-09-25 20:20 ` cvs-commit at gcc dot gnu.org 2023-11-13 16:17 ` jakub at gcc dot gnu.org 2023-11-13 18:27 ` vmakarov at gcc dot gnu.org 2023-11-30 8:23 ` [Bug middle-end/111497] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-30 11:44 ` cvs-commit at gcc dot gnu.org 2024-06-12 12:33 ` [Bug middle-end/111497] [11/12 " 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-111497-4@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).