public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102211] [12 regression] ICE introduced by r12-3277 Date: Mon, 13 Sep 2021 17:43:49 +0000 [thread overview] Message-ID: <bug-102211-4-l62NgcBvB2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102211-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102211 --- Comment #10 from Jim Wilson <wilson at gcc dot gnu.org> --- I attached a patch which is my proposed solution to the RISC-V backend. It adds a new f_register_operand predicate and modifies patterns that use the f constraint to use it instead of register_operand. This was tested with an default language gcc build, glibc build, and glibc check on an unmatched running OpenEmbedded. And an all language gcc build, glibc build, and glibc check on an unleashed running Fedora with an old 4.15 kernel. Both succeeded as well as expected. I'll be trying gcc check next. Meanwhile, the validate_subregs patch was reverted, so we don't immediately need this to fix build errors. But it still might be useful if validate_subregs changes again. Or if it happens to give better code, though I think it won't do anything if validate_subregs is rejecting the subregs we are checking for in f_register_operand.
next prev parent reply other threads:[~2021-09-13 17:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-06 2:53 [Bug target/102211] New: " crazylht at gmail dot com 2021-09-06 4:38 ` [Bug target/102211] " crazylht at gmail dot com 2021-09-06 4:50 ` crazylht at gmail dot com 2021-09-07 8:00 ` [Bug target/102211] [12 regression] " schwab@linux-m68k.org 2021-09-07 8:06 ` pinskia at gcc dot gnu.org 2021-09-08 5:55 ` wilson at gcc dot gnu.org 2021-09-09 23:49 ` Andrew Waterman 2021-09-08 5:55 ` wilson at gcc dot gnu.org 2021-09-09 5:31 ` wilson at gcc dot gnu.org 2021-09-09 23:30 ` segher at gcc dot gnu.org 2021-09-09 23:50 ` andrew at sifive dot com 2021-09-10 21:55 ` cvs-commit at gcc dot gnu.org 2021-09-13 17:35 ` wilson at gcc dot gnu.org 2021-09-13 17:43 ` wilson at gcc dot gnu.org [this message] 2022-01-17 13:33 ` rguenth at gcc dot gnu.org 2022-01-17 13:34 ` rguenth 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-102211-4-l62NgcBvB2@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).