public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98601] [8/9/10/11 Regression] aarch64: ICE in rtx_addr_can_trap_p_1, at rtlanal.c:467 Date: Wed, 31 Mar 2021 11:41:45 +0000 [thread overview] Message-ID: <bug-98601-4-PxunlB18DH@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|rtl-optimization |target --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Note for 'm' constraints (*b) might be preferred over (*(non-void *)b), esp. if used in address context. The generic code rejects it on x86_64 here: #1 0x0000000000a8c37c in build_asm_expr (loc=262658, string=<string_cst 0x7ffff66b00d8>, outputs=<tree_list 0x7ffff669c9d8>, inputs=<tree 0x0>, clobbers=<tree 0x0>, labels=<tree 0x0>, simple=false, is_inline=false) at /home/rguenther/src/gcc3/gcc/c/c-typeck.c:10669 10669 error_at (loc, "invalid use of void expression"); (gdb) l 10664 output = error_mark_node; 10665 if (!(!allows_reg && allows_mem) 10666 && output != error_mark_node 10667 && VOID_TYPE_P (TREE_TYPE (output))) 10668 { 10669 error_at (loc, "invalid use of void expression"); 10670 output = error_mark_node; but it looks like Q is a memory constraint on arm? If so then I don't see why it should be invalid.
next prev parent reply other threads:[~2021-03-31 11:41 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 ` rguenth at gcc dot gnu.org [this message] 2021-03-31 11:50 ` 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 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-PxunlB18DH@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).