From: Paul Brook <paul@codesourcery.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sourceware.org, Nick Clifton <nickc@redhat.com>
Subject: Re: PATCH: Add --alt-nops=short|long to x86/x86-64 assemblers
Date: Thu, 15 Jun 2006 15:28:00 -0000 [thread overview]
Message-ID: <200606151615.03652.paul@codesourcery.com> (raw)
In-Reply-To: <20060615150347.GD7470@lucon.org>
> > FWIW I've found it more useful to add .cpu and/or .arch assembly
> > directives. Handling the gcc spec strings for commandline controls and
> > making sure the gcc and gas defaults are consistent can get painful,
> > especially if gcc has several different ways of specifying the cpu
> > variant.
>
> x86/x86-64 assembler support .arch. But I don't think gcc uses it. I
> am not sure how well it will work with existing code bases if gcc
> starts generating .arch.
That's what configure checks are for.
Paul
next prev parent reply other threads:[~2006-06-15 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 20:45 H. J. Lu
2006-06-14 8:30 ` Nick Clifton
2006-06-14 15:14 ` H. J. Lu
2006-06-14 17:20 ` Nick Clifton
2006-06-14 18:07 ` H. J. Lu
2006-06-15 8:10 ` Nick Clifton
2006-06-15 14:51 ` Paul Brook
2006-06-15 15:15 ` H. J. Lu
2006-06-15 15:28 ` Paul Brook [this message]
2006-06-15 16:20 ` H. J. Lu
2006-06-15 17:08 ` Paul Brook
2006-06-15 17:41 ` H. J. Lu
2006-06-15 18:45 ` Paul Brook
2006-06-15 18:58 ` H. J. Lu
2006-06-15 19:02 ` Paul Brook
2006-06-16 7:27 ` PATCH: Add -march=/-mtune= to x86 assembler H. J. Lu
2006-06-16 15:26 ` H. J. Lu
2006-06-15 15:00 ` PATCH: Add --alt-nops=short|long to x86/x86-64 assemblers H. J. Lu
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=200606151615.03652.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=hjl@lucon.org \
--cc=nickc@redhat.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).