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 middle-end/46479] "+m" (*regs) : "a" (regs) doesn't use (%eax) for the MEM
Date: Mon, 15 Nov 2010 20:02:00 -0000	[thread overview]
Message-ID: <bug-46479-4-C8vHIONnzY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46479-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[4.4/4.5/4.6 Regression]    |"+m" (*regs) : "a" (regs)
                   |"+m" (*regs) : "a" (regs)   |doesn't use (%eax) for the
                   |doesn't use (%eax) for the  |MEM
                   |MEM                         |

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-15 19:54:23 UTC ---
(In reply to comment #3)
> > In any case, having a way to express some memory is clobbered without actually
> > forcing its address to be passed to the inline asm might be useful too.
> Yea.  I'm assuming that clobbers still force generation of the address?

Clobbers are just strings, so they don't force generation of address, but can't
express that some particular memory is read or written.

> And presumably we can't model the use of a memory location in the 
> clobber which might argue we need a "uses" argument to asms...

Perhaps.


  parent reply	other threads:[~2010-11-15 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  9:20 [Bug middle-end/46479] New: [4.4/4.5/4.6 Regression] " jakub at gcc dot gnu.org
2010-11-15  9:49 ` [Bug middle-end/46479] " jakub at gcc dot gnu.org
2010-11-15 14:40 ` law at redhat dot com
2010-11-15 15:08 ` jakub at gcc dot gnu.org
2010-11-15 18:34 ` law at redhat dot com
2010-11-15 20:02 ` jakub at gcc dot gnu.org [this message]
2011-04-16 11:23 ` [Bug middle-end/46479] " jakub at gcc dot gnu.org
2011-04-28 16:36 ` rguenth at gcc dot gnu.org
2021-08-12  5:37 ` [Bug inline-asm/46479] " pinskia 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-46479-4-C8vHIONnzY@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).