public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39620] wrong assumption of clobbered registers of inline assembly
Date: Fri, 03 Apr 2009 08:11:00 -0000	[thread overview]
Message-ID: <20090403081126.29182.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39620-16316@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jakub at gcc dot gnu dot org  2009-04-03 08:11 -------
User error, if you don't tell gcc that %edi is clobbered, obviously it can
assume it hasn't.
As rep stosl modifies both %ecx and %edi, you can write e.g.:
int tmp1, tmp2;
asm volatile("xor %%eax,%%eax\n\trep stosl" : "=c" (tmp1), "=D" (tmp2) : "0"
(count), "1" (dst) : "%eax", "cc", "memory");
or:
asm volatile("xor %%eax,%%eax\n\trep stosl" : "+c" (count), "+D" (dst) : :
"%eax", "cc", "memory");
if you don't mind that the count and dst variables will change.
Also note that __builtin_memset (dst, '\0', count); will in most cases
result in more optimal code for your CPU, hardcoding these in assembly is
usually a bad idea.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39620


  reply	other threads:[~2009-04-03  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  7:55 [Bug c/39620] New: " codemasterhs at yahoo dot de
2009-04-03  8:11 ` jakub at gcc dot gnu dot org [this message]
2009-04-03  8:30 ` [Bug c/39620] " codemasterhs at yahoo dot de

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=20090403081126.29182.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).