From: Andi Kleen <ak@muc.de>
To: Mike Stump <mrs@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Visual C++ style inline asms
Date: Wed, 15 Jun 2005 01:29:00 -0000 [thread overview]
Message-ID: <m1oea89zlo.fsf@muc.de> (raw)
In-Reply-To: <5727F533-27A6-49B7-8D48-CEFC6FF6768B@apple.com> (Mike Stump's message of "Tue, 14 Jun 2005 18:25:00 -0700")
Mike Stump <mrs@apple.com> writes:
> Any objections to adding Visual C++ style inline asms?
Doesn't that need support to parse assembly? (= essentially
a builtin assembler). How else would the compiler
know what registers are clobbered and where to put input/output
variables?
All compilers i've seen who supported that had builtin
assemblers.
-Andi
next prev parent reply other threads:[~2005-06-15 1:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 1:25 Mike Stump
2005-06-15 1:26 ` Andrew Pinski
2005-06-15 1:29 ` Daniel Jacobowitz
2005-06-15 22:46 ` Mike Stump
2005-06-15 22:56 ` Steven Bosscher
2005-06-15 5:08 ` Richard Henderson
2005-06-15 14:35 ` Graham Stott
2005-06-15 20:56 ` Mike Stump
2005-06-15 21:06 ` Mike Stump
2005-06-18 2:47 ` Michael Meissner
2005-06-15 1:29 ` Andi Kleen [this message]
2005-06-15 22:27 ` Mike Stump
2005-06-15 2:39 ` Bobby McNulty
2005-06-15 11:36 ` Ranjit Mathew
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=m1oea89zlo.fsf@muc.de \
--to=ak@muc.de \
--cc=gcc@gcc.gnu.org \
--cc=mrs@apple.com \
/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).