From: Bob Plantz <plantz@cds1.net>
To: Andrew Haley <aph@redhat.com>
Cc: Robin-Vossen <robin-vossen@hotmail.com>, gcc-help@gcc.gnu.org
Subject: Re: GNU C++ Inline Assembler
Date: Tue, 12 Aug 2008 01:08:00 -0000 [thread overview]
Message-ID: <1218489833.5989.6.camel@bob-desktop> (raw)
In-Reply-To: <48A08513.6050103@redhat.com>
On Mon, 2008-08-11 at 19:29 +0100, Andrew Haley wrote:
> Sure, but it massively de-optimizes the code. If you want the best
> performance -- and if you're using asm I guess you do -- you'll
> want to use GNU-style asm.
>
> Andrew.
How can that be? The thing that matters is the machine code. Both
syntaxes generate exactly the same machine code.
Bob
next prev parent reply other threads:[~2008-08-11 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 21:39 Robin-Vossen
2008-08-11 6:37 ` Bob Plantz
2008-08-11 16:35 ` Robin-Vossen
2008-08-11 16:59 ` David Daney
2008-08-11 21:24 ` Andrew Haley
2008-08-12 1:08 ` Bob Plantz [this message]
2008-08-12 2:29 ` Brian Dessent
2008-08-12 8:56 ` Bob Plantz
2008-08-13 17:27 ` Robin-Vossen
2008-08-12 15:26 ` Ian Lance Taylor
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=1218489833.5989.6.camel@bob-desktop \
--to=plantz@cds1.net \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=robin-vossen@hotmail.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).