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/99766] [11 Regression] ICE: unable to generate reloads with SVE code since r11-7807-gbe70bb5e Date: Fri, 26 Mar 2021 17:12:44 +0000 [thread overview] Message-ID: <bug-99766-4-vqrUaXhYYU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99766-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99766 --- Comment #8 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:0d37e2d3ead072ba57e03fcb97a041504a22e721 commit r11-7864-g0d37e2d3ead072ba57e03fcb97a041504a22e721 Author: Vladimir Makarov <vmakarov@redhat.com> Date: Fri Mar 26 17:09:24 2021 +0000 [PR99766] Consider relaxed memory associated more with memory instead of special memory. Relaxed memory should be considered more like memory then special memory. gcc/ChangeLog: PR target/99766 * ira-costs.c (record_reg_classes): Put case with CT_RELAXED_MEMORY adjacent to one with CT_MEMORY. * ira.c (ira_setup_alts): Ditto. * lra-constraints.c (process_alt_operands): Ditto. * recog.c (asm_operand_ok): Ditto. * reload.c (find_reloads): Ditto. gcc/testsuite/ChangeLog: PR target/99766 * g++.target/aarch64/sve/pr99766.C: New.
next prev parent reply other threads:[~2021-03-26 17:12 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 9:47 [Bug target/99766] New: ICE: unable to generate reloads with SVE code ktkachov at gcc dot gnu.org 2021-03-25 9:47 ` [Bug target/99766] [11 Regression] " ktkachov at gcc dot gnu.org 2021-03-25 10:05 ` acoplan at gcc dot gnu.org 2021-03-25 10:06 ` acoplan at gcc dot gnu.org 2021-03-25 11:06 ` [Bug target/99766] [11 Regression] ICE: unable to generate reloads with SVE code since r11-7807-gbe70bb5e acoplan at gcc dot gnu.org 2021-03-25 15:23 ` vmakarov at gcc dot gnu.org 2021-03-25 21:14 ` rsandifo at gcc dot gnu.org 2021-03-26 1:03 ` vmakarov at gcc dot gnu.org 2021-03-26 11:57 ` acoplan at gcc dot gnu.org 2021-03-26 17:12 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-26 17:27 ` vmakarov at gcc dot gnu.org 2021-03-29 9:25 ` ktkachov at gcc dot gnu.org 2022-01-01 8:48 ` cvs-commit at gcc dot gnu.org 2022-01-01 8:48 ` 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-99766-4-vqrUaXhYYU@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).