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 rtl-optimization/98601] [8/9/10 Regression] aarch64: ICE in rtx_addr_can_trap_p_1, at rtlanal.c:467
Date: Tue, 20 Apr 2021 09:45:53 +0000 [thread overview]
Message-ID: <bug-98601-4-CglGZhI2r3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98601
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:e68ac8c2b46997af1464f2549ac520a192c928b1
commit r10-9723-ge68ac8c2b46997af1464f2549ac520a192c928b1
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sat Apr 10 12:46:09 2021 +0200
rtlanal: Another fix for VOIDmode MEMs [PR98601]
This is a sequel to the PR85022 changes, inline-asm can (unfortunately)
introduce VOIDmode MEMs and in PR85022 they have been changed so that
we don't pretend we know their size (as opposed to assuming they have
zero size).
This time we ICE in rtx_addr_can_trap_p_1 because it assumes that
all memory but BLKmode has known size. The patch just treats VOIDmode
MEMs like BLKmode in that regard. And, the STRICT_ALIGNMENT change
is needed because VOIDmode has GET_MODE_SIZE of 0 and we don't want to
check if something is a multiple of 0.
2021-04-10 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/98601
* rtlanal.c (rtx_addr_can_trap_p_1): Allow in assert unknown size
not just for BLKmode, but also for VOIDmode. For STRICT_ALIGNMENT
unaligned_mems handle VOIDmode like BLKmode.
* gcc.dg/torture/pr98601.c: New test.
(cherry picked from commit 7a493fcd27d6a1af896c4f5ef4ab1e0afe8a839d)
next prev parent reply other threads:[~2021-04-20 9:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 13:08 [Bug rtl-optimization/98601] New: " acoplan at gcc dot gnu.org
2021-03-31 10:30 ` [Bug rtl-optimization/98601] [8/9/10/11 Regression] " acoplan at gcc dot gnu.org
2021-03-31 11:00 ` acoplan at gcc dot gnu.org
2021-03-31 11:41 ` [Bug target/98601] " rguenth at gcc dot gnu.org
2021-03-31 11:50 ` [Bug rtl-optimization/98601] " rguenth at gcc dot gnu.org
2021-03-31 12:51 ` acoplan at gcc dot gnu.org
2021-04-09 8:05 ` rguenth at gcc dot gnu.org
2021-04-09 9:16 ` jakub at gcc dot gnu.org
2021-04-09 9:28 ` jakub at gcc dot gnu.org
2021-04-10 10:47 ` cvs-commit at gcc dot gnu.org
2021-04-10 10:50 ` [Bug rtl-optimization/98601] [8/9/10 " jakub at gcc dot gnu.org
2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-20 9:52 ` [Bug rtl-optimization/98601] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` jakub 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-98601-4-CglGZhI2r3@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).