From: Nick Clifton <nickc@redhat.com>
To: Michael Snyder <msnyder@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 16:15:00 -0000 [thread overview]
Message-ID: <m3u1bl3az3.fsf@redhat.com> (raw)
In-Reply-To: <3ECBE1AE.CA5C52EF@redhat.com> (Michael Snyder's message of "Wed, 21 May 2003 13:29:34 -0700")
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 ? 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.
> 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.
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 ?
Cheers
Nick
next prev parent reply other threads:[~2003-05-23 16:15 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 [this message]
2003-05-23 19:44 ` Michael Snyder
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=m3u1bl3az3.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dvenkat@noida.hcltech.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kazu@cs.umass.edu \
--cc=msnyder@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