From: Joe Buck <jbuck@Synopsys.COM>
To: dje@watson.ibm.com (David Edelsohn)
Cc: jbuck@Synopsys.COM, rth@cygnus.com, rearnsha@arm.com,
mrs@wrs.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: <199902011854.KAA04451@atrus.synopsys.com> (raw)
Message-ID: <19990228225300.DS7e_XHUlbpV1u7nIhbyVcpJQUx2nrbfhcmPQBUOStE@z> (raw)
In-Reply-To: <9902011816.AA33418@marc.watson.ibm.com>
> The POWER and PowerPC architecture do not describe a nested set
> which is exactly what is assumed by this entire -march= discussion. You
> and Richard and others are relying on the fact that -march=X is a complete
> subset of -march=X+1. On POWER and PowerPC that is not the case.
I am doing no such thing! It appears that this is the source of your
misunderstanding (that is, you are not understanding what I am proposing).
Nonoverlapping sets will work fine.
You seem to be assuming that architectures and specific processors would
have the same names. They don't need to. Perhaps "architecture" is a
confusing here because you are insisting that all PowerPCs have the same
architecture even though they clearly do not: if some have graphics
extensions and some do not, that is an architectural extension. Sun
marketing says v7 and v8 are different architectures even though the
differences are quite small; evidently the PowerPC marketing guys want
to use the language in a different way.
As for the rest of it, if you can't discuss this issue without getting
so emotional, you're working too hard. I'm not going to argue with you any
more.
next prev parent reply other threads:[~1999-02-28 22: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
[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 [this message]
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=199902011854.KAA04451@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=dje@watson.ibm.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.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).