public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/97708] Inline asm does not use the local register asm specified with register ... asm() as input
Date: Wed, 04 Nov 2020 18:17:32 +0000	[thread overview]
Message-ID: <bug-97708-4-yzOoc8rRZb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97708-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97708

Segher Boessenkool <segher at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |FIXED

--- Comment #23 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The user said that foo should be in xmm1 when used in an asm.  That is
what local register asm does, nothing more, nothing less.

Reloading it is never allowed.

  parent reply	other threads:[~2020-11-04 18:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 19:58 [Bug inline-asm/97708] New: " bp at alien8 dot de
2020-11-03 20:10 ` [Bug inline-asm/97708] " pinskia at gcc dot gnu.org
2020-11-03 20:16 ` bp at alien8 dot de
2020-11-03 20:39 ` segher at gcc dot gnu.org
2020-11-03 20:41 ` pinskia at gcc dot gnu.org
2020-11-03 20:55 ` segher at gcc dot gnu.org
2020-11-03 21:01 ` jakub at gcc dot gnu.org
2020-11-03 21:15 ` bp at alien8 dot de
2020-11-03 22:09 ` jakub at gcc dot gnu.org
2020-11-04  8:29 ` rguenth at gcc dot gnu.org
2020-11-04  8:51 ` jakub at gcc dot gnu.org
2020-11-04 12:13 ` bp at alien8 dot de
2020-11-04 12:20 ` jakub at gcc dot gnu.org
2020-11-04 12:36 ` bp at alien8 dot de
2020-11-04 12:44 ` jakub at gcc dot gnu.org
2020-11-04 12:48 ` jakub at gcc dot gnu.org
2020-11-04 12:55 ` bp at alien8 dot de
2020-11-04 12:58 ` jakub at gcc dot gnu.org
2020-11-04 13:08 ` bp at alien8 dot de
2020-11-04 17:39 ` segher at gcc dot gnu.org
2020-11-04 17:40 ` jakub at gcc dot gnu.org
2020-11-04 17:52 ` segher at gcc dot gnu.org
2020-11-04 17:56 ` jakub at gcc dot gnu.org
2020-11-04 18:17 ` segher at gcc dot gnu.org [this message]
2020-11-05 10:30 ` amonakov at gcc dot gnu.org
2020-11-05 11:04 ` jakub at gcc dot gnu.org
2020-11-05 12:18 ` rguenth at gcc dot gnu.org
2020-11-05 16:02 ` segher at gcc dot gnu.org
2020-11-05 20:34 ` segher at gcc dot gnu.org
2020-11-05 20:38 ` segher at gcc dot gnu.org
2020-11-06 13:23 ` amonakov 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-97708-4-yzOoc8rRZb@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).