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 c/100501] ICE: segmentation fault on embedded asm code Date: Tue, 11 May 2021 06:15:09 +0000 [thread overview] Message-ID: <bug-100501-4-8Qwr7ZPm3Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100501-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100501 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unknown |12.0 Target| |x86_64-*-* Keywords| |accepts-invalid --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- So the asm input is a BIND_EXPR, that's not valid - ({ }) could be valid but then sth converted that to a BIND_EXPR. Note the specific ({ }) does not have a value.
next prev parent reply other threads:[~2021-05-11 6:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-10 12:09 [Bug c/100501] New: " cnsun at uwaterloo dot ca 2021-05-11 6:15 ` rguenth at gcc dot gnu.org [this message] 2021-05-11 22:57 ` [Bug c/100501] " pinskia at gcc dot gnu.org 2021-05-13 4:15 ` cnsun at uwaterloo dot ca 2021-07-19 23:20 ` pinskia at gcc dot gnu.org 2021-07-22 23:19 ` pinskia at gcc dot gnu.org 2021-07-24 2:20 ` [Bug c/100501] ICE with inline-asm and void statement expression cnsun at uwaterloo dot ca 2021-12-26 10:44 ` [Bug c/100501] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-20 13:54 ` rguenth at gcc dot gnu.org 2022-05-27 9:45 ` [Bug c/100501] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-07-07 10:39 ` [Bug c/100501] [11/12/13/14 " rguenth 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-100501-4-8Qwr7ZPm3Y@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).