From: Andrew STUBBS <andrew.stubbs@st.com>
To: "'Nick Clifton'" <nickc@redhat.com>
Cc: "'Alexandre Oliva'" <aoliva@redhat.com>,
<binutils@sources.redhat.com>,
"'Joern RENNECKE'" <joern.rennecke@st.com>
Subject: RE: Broken SH2a patches
Date: Thu, 06 Jan 2005 11:28:00 -0000 [thread overview]
Message-ID: <017c01c4f3e2$ecb09350$0d0f81a4@uk.w2k.superh.com> (raw)
In-Reply-To: <41C70ABC.8050903@redhat.com>
There appears to be another mistake in the inheritance. The SH4 descends
from the SH2A-nofpu which can't be right.
Here is a corrected tree:
SH1
|
SH2
.------------'|`--------------------------------.
/ | \
SH-DSP SH3-nommu/SH2A-nofpu SH2E
| | |`--------------------. |
| | | \|
| SH3-nommu SH4-nm-nf/SH2A-nofpu SH3E/SH2A
| |\ | | | |
| | `------. | SH2A-nofpu | SH4/SH2A
| | \| \ | | |
| SH3 SH4-nommu-nofpu `---------+--. | |
| /|\ | | \| |
| .-----------' | `--------+---------------------. | SH2A |
|/ | / \| |
| | .-------' | |
| |/ | |
SH3-dsp SH4-nofpu SH3E |
| |`-------------------------------. | .-----'
| | \|/
| SH4A-nofpu SH4
| .------------' `-------------------------------. |
|/ \|
SH4AL-dsp SH4A
*/
/* Central branches. */
#define arch_sh1_up (arch_sh1 \
| arch_sh2_up)
#define arch_sh2_up (arch_sh2 \
| arch_sh2e_up \
| arch_sh2a_nofpu_or_sh3_nommu_up \
| arch_sh_dsp_up)
#define arch_sh2a_nofpu_or_sh3_nommu_up (arch_sh2a_nofpu_or_sh3_nommu
\
| arch_sh2a_nofpu_or_sh4_nommu_nofpu_up \
| arch_sh2a_or_sh3e_up \
| arch_sh3_nommu_up)
#define arch_sh2a_nofpu_or_sh4_nommu_nofpu_up
(arch_sh2a_nofpu_or_sh4_nommu_nofpu \
| arch_sh2a_nofpu_up \
| arch_sh4_nommu_nofpu_up)
#define arch_sh2a_nofpu_up (arch_sh2a_nofpu \
| arch_sh2a_up)
#define arch_sh3_nommu_up (arch_sh3_nommu \
| arch_sh3_up \
| arch_sh4_nommu_nofpu_up)
#define arch_sh3_up (arch_sh3 \
| arch_sh3e_up \
| arch_sh3_dsp_up \
| arch_sh4_nofp_up)
#define arch_sh4_nommu_nofpu_up (arch_sh4_nommu_nofpu \
| arch_sh4_nofp_up)
#define arch_sh4_nofp_up (arch_sh4_nofpu \
| arch_sh4_up \
| arch_sh4a_nofp_up)
#define arch_sh4a_nofp_up (arch_sh4a_nofpu \
| arch_sh4a_up \
| arch_sh4al_dsp_up)
/* Right branches. */
#define arch_sh2e_up (arch_sh2e \
| arch_sh2a_or_sh3e_up)
#define arch_sh2a_or_sh3e_up (arch_sh2a_or_sh3e \
| arch_sh2a_or_sh4_up \
| arch_sh3e_up)
#define arch_sh2a_or_sh4_up (arch_sh2a_or_sh4 \
| arch_sh2a_up \
| arch_sh4_up)
#define arch_sh2a_up (arch_sh2a)
#define arch_sh3e_up (arch_sh3e \
| arch_sh4_up)
#define arch_sh4_up (arch_sh4 \
| arch_sh4a_up)
#define arch_sh4a_up (arch_sh4a)
/* Left branch. */
#define arch_sh_dsp_up (arch_sh_dsp \
| arch_sh3_dsp_up)
#define arch_sh3_dsp_up (arch_sh3_dsp \
| arch_sh4al_dsp_up)
#define arch_sh4al_dsp_up (arch_sh4al_dsp)
--
Andrew Stubbs
andrew.stubbs@st.com
andrew.stubbs@superh.com
next prev parent reply other threads:[~2005-01-06 11:28 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
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 [this message]
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='017c01c4f3e2$ecb09350$0d0f81a4@uk.w2k.superh.com' \
--to=andrew.stubbs@st.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=joern.rennecke@st.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).