public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105046] [enhancement] Allow inline-assembly clobbers to overlap inputs Date: Thu, 24 Mar 2022 21:16:22 +0000 [thread overview] Message-ID: <bug-105046-4-B7atnawCeA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105046-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105046 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Sure, but it doesn't force the input to be an lvalue. You can add variables even in macros in statement expressions, #define FOO(whatever) \ ({ int dummy; __asm ("" : "=c" (dummy) : ...); retval; })
next prev parent reply other threads:[~2022-03-24 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 18:45 [Bug c/105046] New: " ehem+gccbugs at m5p dot com 2022-03-24 19:10 ` [Bug middle-end/105046] " pinskia at gcc dot gnu.org 2022-03-24 19:11 ` pinskia at gcc dot gnu.org 2022-03-24 19:27 ` jakub at gcc dot gnu.org 2022-03-24 21:11 ` [Bug c/105046] " ehem+gccbugs at m5p dot com 2022-03-24 21:16 ` jakub at gcc dot gnu.org [this message] 2022-03-24 21:51 ` ehem+gccbugs at m5p dot com 2022-03-25 21:14 ` ehem+gccbugs at m5p dot com
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-105046-4-B7atnawCeA@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).