public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ilya.lesokhin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/43998] inline assembler: can't set clobbering for input register
Date: Mon, 08 Apr 2013 08:04:00 -0000 [thread overview]
Message-ID: <bug-43998-4-1LaWGfQCUw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43998-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43998
Ilya Lesokhin <ilya.lesokhin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ilya.lesokhin at gmail dot
| |com
--- Comment #13 from Ilya Lesokhin <ilya.lesokhin at gmail dot com> 2013-04-08 08:04:28 UTC ---
Andrew Pinski said:
> Use an output register that says it clobbers that register.
This indeed works for normal inline assembler, but it doesn't work for asm goto
which currently doesn't have outputs.
maybe the Bug should be reopened for newer versions of GCC?
next parent reply other threads:[~2013-04-08 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43998-4@http.gcc.gnu.org/bugzilla/>
2013-04-08 8:04 ` ilya.lesokhin at gmail dot com [this message]
2010-05-06 6:37 [Bug inline-asm/43998] New: " socketpair at gmail dot com
2010-05-06 7:11 ` [Bug inline-asm/43998] " ubizjak at gmail dot com
2010-05-06 8:07 ` jakub at gcc dot gnu dot org
2010-05-06 11:00 ` socketpair at gmail dot com
2010-05-06 11:31 ` rguenth at gcc dot gnu dot org
2010-05-06 11:41 ` socketpair at gmail dot com
2010-05-06 13:09 ` hjl dot tools at gmail dot com
2010-05-06 13:42 ` socketpair at gmail dot com
2010-05-06 13:56 ` rguenth at gcc dot gnu dot org
2010-05-06 15:04 ` socketpair at gmail dot com
2010-05-14 2:45 ` pinskia at gcc dot gnu dot org
2010-05-14 6:31 ` socketpair at gmail dot com
2010-05-14 7:11 ` ebotcazou at gcc dot gnu dot 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-43998-4-1LaWGfQCUw@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).