From: Joern RENNECKE <joern.rennecke@st.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: "'Nick Clifton'" <nickc@redhat.com>,
"'Alexandre Oliva'" <aoliva@redhat.com>,
binutils@sources.redhat.com
Subject: Re: Broken SH2a patches
Date: Mon, 08 Nov 2004 16:27:00 -0000 [thread overview]
Message-ID: <418F9E6A.90001@st.com> (raw)
In-Reply-To: <008401c4c5a5$8db854c0$180f81a4@uk.w2k.superh.com>
> I don't like the name 'fake', but I'm not sure what else to suggest.
Perhaps
>sh2+, sh2e+, sh2++ and sh2e++ (or sh2+shift, sh2e+shift+fsqrt,
>sh2+shift+pref and sh2e+double). Of course '+' won't work in C ... hmmm.
>
>Unfortunately a lot of libraries etc. will end up labelled with these 'fake'
>architectures so it is important that the name means something.
>
When there are only one ot two simple features added, it seems most
future-proof to
just enumerate them. I.e. the 'fake1' adds dynamic shift to SH2,
'fake2' adds dynamic shift and
fsqrt.s to SH2E, 'fake3' adds dynamic shift and prefetch to SH2.
'fake4', however, adds dynamic shift, fsqrt.s, prefetch, and a plethora
of double precision arithmetic
instructions and ancillary instructions to that. So I think we better
name that one from the
intersection that generates it, i.e. SH4_SH2A .
You can probably draw this more nicely...
SH2
.------------'|`--------------------.
/ | \
SH2 SH2_dshift SH2E
(dsp) / \ \ |
| / \ \_____________ |
| / \ \ |
| / \ \ |
| / SH3 \ |
| / (nommu) SH2E_dshift_sqrt
| SH2_dshift_pref |\ /|
| | \ | \ / |
| | \ | \ / |
| | \ | SH3 / |
| | \ | /|\ / |
| | \ | / | \ / |
| | \ .!./ | \ / |
| | . \ | | \ / |
| SH2A . SH4 | \ / SH4_SH2A
| (nofpu) . (nommu) | SH3E / |
| | . (nofpu) | /\ / |
| ...+..... | .--' | \ / |
| / | | / | \ / |
SH3 | SH4 | X |
(dsp) | (nofpu) | / \ |
| | /\ | / \ |
| | / '---. | / \ /
| | / \ |/ \/
-+---- . SH4A SH4 SH2A <------....
| (nofpu) |
| / \ .-'
| .--------' '---. /
| / \/
SH4AL SH4A
(dsp)
next prev parent reply other threads:[~2004-11-08 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 17:00 Andrew STUBBS
2004-10-28 20:33 ` Alexandre Oliva
2004-10-29 10:39 ` Nick Clifton
2004-10-29 12:11 ` Andrew STUBBS
2004-10-29 12:28 ` [OT] " Dave Korn
2004-10-29 12:59 ` Andrew STUBBS
2004-10-29 13:03 ` Dave Korn
2004-10-29 13:21 ` Andrew STUBBS
2004-10-29 13:59 ` Ian Lance Taylor
2004-10-29 14:35 ` Andrew STUBBS
2004-10-29 14:58 ` Ian Lance Taylor
2004-10-29 15:44 ` Andrew STUBBS
2004-11-08 9:04 ` Nick Clifton
2004-11-08 15:12 ` Andrew STUBBS
2004-11-08 16:27 ` Joern RENNECKE [this message]
2004-11-08 16:36 ` Joern RENNECKE
2004-12-15 17:11 ` Nick Clifton
2004-12-16 13:24 ` Andrew STUBBS
2004-12-20 17:18 ` Nick Clifton
2005-01-05 13:27 ` Andrew STUBBS
2005-01-06 11:28 ` Andrew STUBBS
2005-01-12 16:23 ` Nick Clifton
2005-01-07 12:55 ` Andrew STUBBS
2005-01-10 13:31 ` Joern RENNECKE
2005-01-11 18:01 ` Andrew STUBBS
2004-12-02 12:19 Andrew STUBBS
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=418F9E6A.90001@st.com \
--to=joern.rennecke@st.com \
--cc=andrew.stubbs@st.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.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).