From: Joe Buck <Joe.Buck@synopsys.COM>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Jeffrey A Law <law@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: What to call Intel ia32e processor?
Date: Mon, 01 Mar 2004 19:00:00 -0000 [thread overview]
Message-ID: <20040301110039.G28871@synopsys.com> (raw)
In-Reply-To: <20040301004614.GA7220@lucon.org>; from hjl@lucon.org on Sun, Feb 29, 2004 at 04:46:14PM -0800
On Sun, Feb 29, 2004 at 04:46:14PM -0800, H. J. Lu wrote:
> On Sun, Feb 29, 2004 at 08:40:15PM +0100, Gerald Pfeifer wrote:
> > On Fri, 27 Feb 2004, H. J. Lu wrote:
> > > Currently, when you configure gcc for x86_64-linux, it will tune for
> > > K8. I want a new target, which will tune for Intel ia32e processor by
> > > default. I am using ia32e-linux for the time being.
> >
> > That way a lot of software won't recognize that beast at _all_, neither
> > as i386 nor as amd64 compatible.
>
> I only want it for gcc and you have to use it by hand like
>
> # ../configure ia32e-linux
>
> which will configure gcc to tune for Intel ia32e processor by default.
> Nothing else will be affected.
Please don't inflict that on any external users. As others have said,
the way we handle the different flavors of one processor family is with
--with-cpu.
next prev parent reply other threads:[~2004-03-01 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 17:50 H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap
2004-02-27 18:16 ` law
2004-02-27 18:17 ` Randy.Dunlap
2004-02-27 19:10 ` H. J. Lu
2004-02-29 22:17 ` Gerald Pfeifer
2004-03-01 0:46 ` H. J. Lu
2004-03-01 1:29 ` Daniel Jacobowitz
2004-03-01 19:00 ` Joe Buck [this message]
2004-03-01 19:47 ` H. J. Lu
2004-03-01 9:17 ` Allan Sandfeld
2004-03-01 16:53 ` H. J. Lu
2004-02-27 18:17 ` Karel Gardas
2004-02-27 18:25 ` Paolo Carlini
2004-02-27 18:41 ` law
2004-02-27 18:52 ` Daniel Berlin
2004-02-27 22:41 ` Arnaud Charlet
2004-02-28 23:25 ` Mike Stump
2004-02-27 21:45 ` Guillermo Ballester Valor
2004-02-27 21:15 ` Jakub Jelinek
2004-02-27 22:49 ` Christoph Hellwig
2004-03-01 7:05 ` Alexandre Oliva
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=20040301110039.G28871@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=hjl@lucon.org \
--cc=law@redhat.com \
--cc=rddunlap@osdl.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).