From: Jeffrey A Law <law@hurl.cygnus.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: drepper@cygnus.com, egcs@cygnus.com
Subject: Re: mutex in frame code
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <22596.917373267@hurl.cygnus.com> (raw)
Message-ID: <19990131235800.6yABzcXRLKGPBJP4JokKkxUoKaXOoYHVhhxeqwSMGF8@z> (raw)
In-Reply-To: <199901261754.JAA02030@atrus.synopsys.com>
In message < 199901261754.JAA02030@atrus.synopsys.com >you write:
> That is, the default is -march=i386. But I just noticed that different
> ports (in particular, Sparc and ix86) are using the same -m flag with a
> completely different meaning:
Yes. There was a great uproar on gcc2 a couple years ago about this. I didn't
follow it closely at the time.
>
> Generally, there are two semi-independent flags to be set when dealing
> with processor families: one says which processor to optimize for, one
> says which processor to assume that we have.
Right.
> Thus for the sparc port I can write
> -mtune=v9 -mcpu=v8
>
> to get code that is tuned to run best on v9 (Ultrasparcs) but that
> will run on v8 machines (but will not run on v7 machines).
>
> But for i386, we have -mcpu=x -march=y, and -mcpu for Intel means
> the same as -mtune on Sparc! -march is used to generate code that
> requires a particular processor.
Yup. Quite inconsistent.
jeff
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-25 14:44 Ulrich Drepper
1999-01-26 5:06 ` Jeffrey A Law
1999-01-26 7:48 ` Ulrich Drepper
1999-01-31 23:58 ` Ulrich Drepper
1999-01-26 9:54 ` Joe Buck
1999-01-26 9:57 ` Jeffrey A Law [this message]
1999-01-26 10:23 ` Joe Buck
1999-01-26 10:27 ` David Edelsohn
1999-01-26 10:42 ` Joe Buck
1999-01-26 10:56 ` David Edelsohn
1999-01-26 11:28 ` Joe Buck
1999-01-26 11:44 ` David Edelsohn
1999-01-31 23:58 ` David Edelsohn
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` David Edelsohn
1999-01-26 11:02 ` Nick Ing-Simmons
1999-01-31 23:58 ` Nick Ing-Simmons
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` David Edelsohn
1999-01-26 13:17 ` Gabriel Dos Reis
1999-01-31 23:58 ` Gabriel Dos Reis
1999-01-31 23:58 ` Joe Buck
[not found] ` <36AE692E.A5DD45E6@manhattanproject.com>
1999-01-26 17:27 ` gperf switch Clark Evans
1999-01-26 18:18 ` Alexandre Oliva
1999-01-26 19:57 ` Donn Terry
1999-01-31 23:58 ` Donn Terry
1999-01-31 23:58 ` Alexandre Oliva
1999-01-31 23:58 ` Clark Evans
1999-01-31 23:58 ` mutex in frame code Jeffrey A Law
1999-01-31 23:58 ` Joe Buck
1999-01-31 23:58 ` Jeffrey A Law
1999-01-31 23:58 ` Ulrich Drepper
1999-01-26 13:20 Mike Stump
1999-01-31 23:58 ` Mike Stump
1999-02-01 7:38 ` Richard Earnshaw
[not found] ` < 199902011536.PAA05753@sun52.NIS.cambridge >
1999-02-01 9:35 ` Richard Henderson
[not found] ` < 19990201093544.A18419@cygnus.com >
1999-02-01 9:53 ` David Edelsohn
[not found] ` < 9902011752.AA89026@marc.watson.ibm.com >
1999-02-01 10:07 ` Joe Buck
[not found] ` < 199902011806.KAA02061@atrus.synopsys.com >
1999-02-01 10:16 ` David Edelsohn
[not found] ` < 9902011816.AA33418@marc.watson.ibm.com >
1999-02-01 10:48 ` Zack Weinberg
[not found] ` < 199902011848.NAA27796@blastula.phys.columbia.edu >
1999-02-01 10:54 ` David Edelsohn
[not found] ` < 9902011854.AA89036@marc.watson.ibm.com >
1999-02-01 11:09 ` Joe Buck
[not found] ` < 199902011907.LAA05591@atrus.synopsys.com >
1999-02-01 11:25 ` David Edelsohn
1999-02-28 22:53 ` David Edelsohn
1999-02-28 22:53 ` Joe Buck
1999-02-28 22:53 ` David Edelsohn
1999-02-28 22:53 ` Zack Weinberg
1999-02-01 10:54 ` Joe Buck
1999-02-28 22:53 ` Joe Buck
1999-02-01 23:00 ` Matthias Urlichs
[not found] ` < 19990202080023.B15962@noris.de >
1999-02-02 10:04 ` David Edelsohn
1999-02-28 22:53 ` David Edelsohn
1999-02-28 22:53 ` Matthias Urlichs
1999-02-28 22:53 ` David Edelsohn
1999-02-28 22:53 ` Joe Buck
1999-02-01 10:25 ` Zack Weinberg
[not found] ` < 199902011825.NAA27565@blastula.phys.columbia.edu >
1999-02-01 10:32 ` David Edelsohn
1999-02-28 22:53 ` David Edelsohn
1999-02-28 22:53 ` Zack Weinberg
1999-02-28 22:53 ` David Edelsohn
1999-02-01 9:54 ` Richard Earnshaw
1999-02-28 22:53 ` Richard Earnshaw
1999-02-28 22:53 ` Richard Henderson
1999-02-28 22:53 ` Richard Earnshaw
1999-02-02 10:24 Mike Stump
[not found] ` < 199902021823.KAA13030@kankakee.wrs.com >
1999-02-02 12:40 ` Gavin Romig-Koch
[not found] ` < 14007.25134.285874.916089@cetus.cygnus.com >
1999-02-03 3:30 ` Richard Earnshaw
1999-02-28 22:53 ` Richard Earnshaw
1999-02-28 22:53 ` Gavin Romig-Koch
1999-02-28 22:53 ` Mike Stump
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=22596.917373267@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@Synopsys.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).