public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "umbricola at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/57299] Inline assembly memory dependencies produce spurious loads, register pressure, compilation failures
Date: Wed, 15 May 2013 18:44:00 -0000	[thread overview]
Message-ID: <bug-57299-4-DhV48trend@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57299-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Chris Mihelich <umbricola at gmail dot com> ---
Yes indeed, x is loaded from the stack into edi, and y is loaded from the stack
into esi, as the register variable declarations specified.  That's two
registers.  Where are the other two?


  parent reply	other threads:[~2013-05-15 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 18:08 [Bug inline-asm/57299] New: " umbricola at gmail dot com
2013-05-15 18:14 ` [Bug inline-asm/57299] " pinskia at gcc dot gnu.org
2013-05-15 18:22 ` umbricola at gmail dot com
2013-05-15 18:24 ` pinskia at gcc dot gnu.org
2013-05-15 18:44 ` umbricola at gmail dot com [this message]
2013-05-15 18:53 ` pinskia at gcc dot gnu.org
2013-05-15 19:20 ` umbricola at gmail dot com
2013-05-15 20:16 ` pinskia at gcc dot gnu.org
2013-05-15 21:57 ` umbricola at gmail dot com
2013-05-15 21:59 ` 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-57299-4-DhV48trend@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).