public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <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: Thu, 06 May 2010 13:56:00 -0000 [thread overview]
Message-ID: <20100506135559.31328.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43998-17114@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from rguenth at gcc dot gnu dot org 2010-05-06 13:55 -------
(In reply to comment #7)
> > Just make eax both input and output.
> it's not optimal. gcc will try to preserve new eax value. So it will not use
> eax register in next instructions. If eax is really need, it will save it in
> esi, edi or so on - it's redundant.
Not if you make the output unused by not using it.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43998
next prev parent reply other threads:[~2010-05-06 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <bug-43998-4@http.gcc.gnu.org/bugzilla/>
2013-04-08 8:04 ` ilya.lesokhin at gmail 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=20100506135559.31328.qmail@sourceware.org \
--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).