public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101697] [11/12/13 regression] ICE compiling uClibc-ng for h8300-linux Date: Sun, 16 Oct 2022 19:19:39 +0000 [thread overview] Message-ID: <bug-101697-4-D7zo3bF80R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101697-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101697 --- Comment #6 from Jeffrey A. Law <law at gcc dot gnu.org> --- So this issue has come up again in the context of LRA conversion which happens to trip over the same bug, but with a different testcase. At the core of this problem is reload and LRA will both generate invalid RTL when performing register eliminations. Specifically, they will create an autoinc addressing mode where the incremented/decremented register is used elsewhere in the same insn as a source operand. Such RTL has been considered invalid as long as I can remember. The H8 backend does try to prevent this behavior by checking for this scenario and rejecting such insns in the insn condition. But in both the reload and LRA cases, they make substitutions in the original insn without validating the resulting insn (which would have failed). Even if they did try to validate the resulting insn, neither has a code generation strategy to deal with a failed substitution during register eliminations. Paul K. indicated how the pdp11 port handles these cases with constraints. Using constraints alone was insufficient to fix this problem, but using constraints in conjunction with the existing insn condition checks does seem to fix this problem. I'm currently upstreaming the various bits to make that happen.
next prev parent reply other threads:[~2022-10-16 19:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-30 18:37 [Bug target/101697] New: [11/12 " mikpelinux at gmail dot com 2021-07-30 18:47 ` [Bug target/101697] " pinskia at gcc dot gnu.org 2021-07-31 21:09 ` mikpelinux at gmail dot com 2021-08-03 17:02 ` law at gcc dot gnu.org 2021-08-09 20:26 ` mikpelinux at gmail dot com 2021-08-17 6:15 ` law at gcc dot gnu.org 2021-08-17 6:15 ` law at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-10-16 19:19 ` law at gcc dot gnu.org [this message] 2022-10-17 23:54 ` [Bug target/101697] [11/12/13 " cvs-commit at gcc dot gnu.org 2022-10-17 23:55 ` [Bug target/101697] [11/12 " law at gcc dot gnu.org 2022-10-18 14:39 ` mikpelinux at gmail dot com 2022-12-19 21:59 ` pinskia at gcc dot gnu.org 2023-02-23 23:10 ` pinskia 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-101697-4-D7zo3bF80R@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).