From: Michael Snyder <msnyder@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: kazu@cs.umass.edu, dvenkat@noida.hcltech.com,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [RFA] H8/300sx port for gas, sim, and opcodes (1/5)
Date: Fri, 23 May 2003 19:44:00 -0000 [thread overview]
Message-ID: <3ECE7A13.2ADF77D6@redhat.com> (raw)
In-Reply-To: <m3u1bl3az3.fsf@redhat.com>
Nick Clifton wrote:
>
> Hi Michael,
>
> > This is the first of several posts containing a submission of a port
> > extending the h8/300 tools to cover the new h8300sx architecture.
>
> > The files are so heavily changed that I'm just going to submit them
> > inline, rather than as diffs.
>
> In the future please do not do this. Please submit the diffs
> instead. You can zip/compress/gzip/bzip2 them if necessary, but in
> order to check these patches I had to save out each file, run diff by
> hand and then check the output to see what was happening.
>
> Also - was it really necessary to make such sweeping changes, just in
> order to make a new architecture variant ?
Yep -- the h8sx is pretty radically different from its predecessors.
For instance, the opcode table goes from about 350 entries to 8,400.
It adds about 14 new addressing modes to each instruction.
> I realise that you
> probably were not the one who made all of these changes, but they do
> seem quite extensive and an explanation of why they were necessary
> would have been nice.
Sorry. Big change in architecture.
> > 2003-05-14 Michael Snyder <msnyder@redhat.com>
> > and Bernd Schmidt <bernds@redhat.com>
> > and Alexandre Oliva <aoliva@redhat.com>
> > * opcode/h8300.h: Add h8300sx insns, addressing modes, etc.
>
> Approved - please apply.
>
> Note - please also add an entry in the gas/NEWS file mentioning the
> support for this new architecture.
OK.
> Will there be a further contribution with an extension to the gas
> testsuite for cover the new instructions and addressing modes
> supported by the h8300sx ?
Yes. I thought I'd contribute the architecture changes first,
but I do have a rather large set of gas tests to contribute too.
Michael
next prev parent reply other threads:[~2003-05-23 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 20:29 Michael Snyder
2003-05-23 16:15 ` Nick Clifton
2003-05-23 19:44 ` Michael Snyder [this message]
2003-06-03 21:26 ` Michael Snyder
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=3ECE7A13.2ADF77D6@redhat.com \
--to=msnyder@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dvenkat@noida.hcltech.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kazu@cs.umass.edu \
--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