From: David Edelsohn <dje@watson.ibm.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Richard Earnshaw <rearnsha@arm.com>, Mike Stump <mrs@wrs.com>,
jbuck@Synopsys.COM, law@cygnus.com, drepper@cygnus.com,
egcs@cygnus.com, richard.earnshaw@arm.com
Subject: Re: mutex in frame code
Date: Mon, 01 Feb 1999 09:53:00 -0000 [thread overview]
Message-ID: <9902011752.AA89026@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Richard Henderson <rth@cygnus.com> of "Mon, 01 Feb 1999 09:35:44 PST." < 19990201093544.A18419@cygnus.com >
>>>>> Richard Henderson writes:
Richard> If we commonize on anything, I think it should be `arch' and `tune';
Richard> `cpu' is too ambiguous.
I repeat again that -march= provides the wrong information for the
PowerPC port. One wants a simple way to specify both architecture and
scheduler tuning; -mcpu= provides that information. -march= primarily is
useful for processors in which each chip extended the architecture like
x86 and Alpha, not for processors where an ISA was designed and maintained
like PowerPC.
David
WARNING: multiple messages have this Message-ID
From: David Edelsohn <dje@watson.ibm.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Richard Earnshaw <rearnsha@arm.com>, Mike Stump <mrs@wrs.com>,
jbuck@Synopsys.COM, law@cygnus.com, drepper@cygnus.com,
egcs@cygnus.com, richard.earnshaw@arm.com
Subject: Re: mutex in frame code
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <9902011752.AA89026@marc.watson.ibm.com> (raw)
Message-ID: <19990228225300.YK5jpWGWGgf340cGdhKy0pvQvb-IqRrfJWnKvOyA6oQ@z> (raw)
In-Reply-To: <19990201093544.A18419@cygnus.com>
>>>>> Richard Henderson writes:
Richard> If we commonize on anything, I think it should be `arch' and `tune';
Richard> `cpu' is too ambiguous.
I repeat again that -march= provides the wrong information for the
PowerPC port. One wants a simple way to specify both architecture and
scheduler tuning; -mcpu= provides that information. -march= primarily is
useful for processors in which each chip extended the architecture like
x86 and Alpha, not for processors where an ISA was designed and maintained
like PowerPC.
David
next prev parent reply other threads:[~1999-02-01 9:53 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
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
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
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
1999-01-31 23:58 ` 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
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=9902011752.AA89026@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 \
--cc=mrs@wrs.com \
--cc=rearnsha@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=rth@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).