From: Nick Clifton <nickc@redhat.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: "'Alexandre Oliva'" <aoliva@redhat.com>,
binutils@sources.redhat.com,
"'Joern RENNECKE'" <joern.rennecke@st.com>
Subject: Re: Broken SH2a patches
Date: Wed, 12 Jan 2005 16:23:00 -0000 [thread overview]
Message-ID: <41E550DD.9040005@redhat.com> (raw)
In-Reply-To: <017c01c4f3e2$ecb09350$0d0f81a4@uk.w2k.superh.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi Andrew,
> 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:
Thanks - I have put that into the latest patch (attached) along with a
fix for the other problem you spotted
(arch_sh2a_nofpu_or_sh4_nommu_nofpu being the same as
arch_sh2a_nofpu_or_sh3_nommu). Otherwise this patch is the same as the
previous one with a suitably amended arch_expected.txt for the GAS tests.
> Do you think it worth bothering with any new scheme?
Personally yes - but only if:
a) Someone is willing to put the effort into developing it. I do not
think that it will be a trivial programming exercise and I am not
volunteering, at least not right now.
b) There are more SH variants to come. A bit of crystal ball gazing
is required for this one, but presumably it is quite likely that the SH
line will continue to be developed.
Cheers
Nick
[-- Attachment #2: sh.patch.4.bz2 --]
[-- Type: application/x-bzip2, Size: 8259 bytes --]
next prev parent reply other threads:[~2005-01-12 16:23 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
2005-01-12 16:23 ` Nick Clifton [this message]
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=41E550DD.9040005@redhat.com \
--to=nickc@redhat.com \
--cc=andrew.stubbs@st.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=joern.rennecke@st.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).