From: David Edelsohn <dje@watson.ibm.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: law@cygnus.com, drepper@cygnus.com, egcs@cygnus.com
Subject: Re: mutex in frame code
Date: Tue, 26 Jan 1999 10:56:00 -0000 [thread overview]
Message-ID: <9901261856.AA87156@marc.watson.ibm.com> (raw)
In-Reply-To: <199901261842.KAA05151@atrus.synopsys.com>
>>>>> Joe Buck writes:
Joe> Generally one would not specify an exact processor in -march, but it would
Joe> make sense in -mtune. -march says what instructions I can assume are
Joe> present (and possibly, what restrictions on instruction order for
Joe> processors without interlocks, what few that exist). -mtune says what
Joe> I should optimize for.
And -mcpu specifies an architecture / tuning pair instead of
confusing users and forcing uses to type multiple options where one option
is implied by the other.
POWER and PowerPC do not have evolving architectures. PPC604 is
not a superset of PPC603 which is not a superset of PPC601. "common" is a
special mode for AIX which runs on both POWER and PowerPC architectures,
but no one else does because neither is a a superset of the other.
Will you please try to understand that your clasification does not
apply equally well to all ports and you should not impose it upon everyone?
David
WARNING: multiple messages have this Message-ID
From: David Edelsohn <dje@watson.ibm.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: law@cygnus.com, 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: <9901261856.AA87156@marc.watson.ibm.com> (raw)
Message-ID: <19990131235800.HNnUeExEftDdCnDuNEf8bri14oviiZziAIRsfnVnMLg@z> (raw)
In-Reply-To: <199901261842.KAA05151@atrus.synopsys.com>
>>>>> Joe Buck writes:
Joe> Generally one would not specify an exact processor in -march, but it would
Joe> make sense in -mtune. -march says what instructions I can assume are
Joe> present (and possibly, what restrictions on instruction order for
Joe> processors without interlocks, what few that exist). -mtune says what
Joe> I should optimize for.
And -mcpu specifies an architecture / tuning pair instead of
confusing users and forcing uses to type multiple options where one option
is implied by the other.
POWER and PowerPC do not have evolving architectures. PPC604 is
not a superset of PPC603 which is not a superset of PPC601. "common" is a
special mode for AIX which runs on both POWER and PowerPC architectures,
but no one else does because neither is a a superset of the other.
Will you please try to understand that your clasification does not
apply equally well to all ports and you should not impose it upon everyone?
David
next prev parent reply other threads:[~1999-01-26 10:56 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
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 [this message]
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=9901261856.AA87156@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@Synopsys.COM \
--cc=law@cygnus.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).