public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111225] ICE in curr_insn_transform, unable to generate reloads for xor, since r14-2447-g13c556d6ae84be Date: Thu, 07 Sep 2023 14:04:41 +0000 [thread overview] Message-ID: <bug-111225-4-Hnh3vJhwOa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111225-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111225 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:f7bca44d97ad01b39f9d6e7809df7bf517eeb2fb commit r14-3783-gf7bca44d97ad01b39f9d6e7809df7bf517eeb2fb Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Thu Sep 7 09:59:10 2023 -0400 [LRA]: Don't reuse chosen insn alternative with special memory constraint To speed up GCC, LRA reuses chosen alternative from previous constraint subpass. A spilled pseudo is considered ok for any memory constraint although stack slot assigned to the pseudo later might not satisfy the chosen alternative constraint. As we don't consider all insn alternatives on the subsequent LRA sub-passes, it might result in LRA failure to generate the correct insn. This patch solves the problem. gcc/ChangeLog: PR target/111225 * lra-constraints.cc (goal_reuse_alt_p): New global flag. (process_alt_operands): Set up the flag. Clear flag for chosen alternative with special memory constraints. (process_alt_operands): Set up used insn alternative depending on the flag. gcc/testsuite/ChangeLog: PR target/111225 * gcc.target/i386/pr111225.c: New test.
next prev parent reply other threads:[~2023-09-07 14:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-29 13:01 [Bug target/111225] New: " jamborm at gcc dot gnu.org 2023-08-30 2:12 ` [Bug target/111225] " crazylht at gmail dot com 2023-08-30 2:16 ` crazylht at gmail dot com 2023-08-30 21:31 ` vmakarov at gcc dot gnu.org 2023-09-07 14:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-30 10:46 ` liuhongt 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-111225-4-Hnh3vJhwOa@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).