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/99041] combine creates invalid address which ICEs in decompose_normal_address
Date: Wed, 10 Mar 2021 23:48:21 +0000 [thread overview]
Message-ID: <bug-99041-4-154B5vWMxA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99041
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:336cd08b65ea589bc4acc8c91a4a4c4873363989
commit r10-9430-g336cd08b65ea589bc4acc8c91a4a4c4873363989
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Thu Feb 11 14:15:26 2021 -0600
rs6000: Fix invalid address used in MMA built-in function
The mma_assemble_input_operand predicate is too lenient on the memory
operands it will accept, leading to an ICE when illegitimate addresses
are passed in. The solution is to only accept memory operands with
addresses that are valid for quad word memory accesses. The test case
is a minimized test case from the Eigen library. The creduced test case
is very noisy with respect to warnings, so the test case has added -w to
silence them.
2021-02-11 Peter Bergner <bergner@linux.ibm.com>
gcc/
PR target/99041
* config/rs6000/predicates.md (mma_assemble_input_operand):
Restrict
memory addresses that are legal for quad word accesses.
gcc/testsuite/
PR target/99041
* g++.target/powerpc/pr99041.C: New test.
(cherry picked from commit 2432c47970024db6410708b582a901259dabaae1)
next prev parent reply other threads:[~2021-03-10 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 18:51 [Bug rtl-optimization/99041] New: " bergner at gcc dot gnu.org
2021-02-09 18:52 ` [Bug rtl-optimization/99041] " bergner at gcc dot gnu.org
2021-02-09 19:02 ` jakub at gcc dot gnu.org
2021-02-09 19:13 ` bergner at gcc dot gnu.org
2021-02-09 20:52 ` segher at gcc dot gnu.org
2021-02-09 20:55 ` segher at gcc dot gnu.org
2021-02-10 20:51 ` [Bug target/99041] " bergner at gcc dot gnu.org
2021-02-10 21:27 ` segher at gcc dot gnu.org
2021-02-11 20:16 ` cvs-commit at gcc dot gnu.org
2021-02-11 20:24 ` bergner at gcc dot gnu.org
2021-02-11 21:07 ` bergner at gcc dot gnu.org
2021-03-10 23:48 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-10 23:50 ` bergner 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-99041-4-154B5vWMxA@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: link
Be 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).