public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/98601] [8/9/10/11 Regression] aarch64: ICE in rtx_addr_can_trap_p_1, at rtlanal.c:467 Date: Wed, 31 Mar 2021 12:51:13 +0000 [thread overview] Message-ID: <bug-98601-4-2x4PBnGGHA@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 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2021-03-31 Keywords| |ice-on-valid-code --- Comment #4 from Alex Coplan <acoplan at gcc dot gnu.org> --- richi: thanks for the pointers. I agree it looks like this should be valid. E.g. the very reasonable: void foo(void *p) { asm volatile ("str xzr, %0" : "=Q"(*p)); } gives: foo: str xzr, [x0] ret at -O2 on AArch64. (Dropping the volatile in this case reproduce the ICE.) I bisected the ICE to r8-7484-g532c7a45847f3401e26fa2f07e52613891c80718: commit 532c7a45847f3401e26fa2f07e52613891c80718 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Mar 23 20:55:40 2018 re PR inline-asm/85022 (internal compiler error: in write_dependence_p, at alias.c:3003) PR inline-asm/85022 * emit-rtl.c (init_emit_regs): Indicate that VOIDmode MEMs don't have known size by default.
next prev parent reply other threads:[~2021-03-31 12:51 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 [this message] 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 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-2x4PBnGGHA@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).