public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Fred Cooke <fred.cooke@gmail.com>
To: James Murray <jsm@jsm-net.demon.co.uk>
Cc: binutils@sourceware.org, nick clifton <nickc@redhat.com>
Subject: Re: 68hc11/12/s12x/xgate patch
Date: Mon, 12 Mar 2012 15:26:00 -0000	[thread overview]
Message-ID: <CABZhLO_=6t=8EV5UcKN5LUqz0ZHBjQOqMZQhzNhx2V+HXEmewQ@mail.gmail.com> (raw)
In-Reply-To: <1331564819.2407.61.camel@jsm2>

James,

Two things, for now:

1) Am I correct in saying that this is still one monolithic patch that
makes multiple changes to the port?

2) Am I correct in saying that this is still comprised mostly of a
two-architectures-in-one-port code change?

Regards,

Fred.

On Mon, Mar 12, 2012 at 4:06 PM, James Murray <jsm@jsm-net.demon.co.uk> wrote:
>
> I believe the attached patch remedies the concerns that Nick raised on
> my previous submission.
>
> Plain text NEWS and ChangeLog entries:
>
> bfd/ChangeLog:
> 2012-03-12  James Murray <jsm@jsm-net.demon.co.uk>
>
>    * Add S12X and XGATE co-processor support to m68hc11 target
>    (during period 2008-01 -> 2012-03)
>    Allows S12X and XGATE code to be linked together.
>    * Option to offset S12 addresses into XGATE memory space.
>    * Fix carry bug in IMM16 (IMM8 low/high) relocate.
>
> gas/ChangeLog:
> 2012-03-12  James Murray <jsm@jsm-net.demon.co.uk>
>
>    * Add S12X and XGATE co-processor support to m68hc11 target
>    (during period 2008-01 -> 2012-03)
>    Most S12X extensions supported (new opcodes, extended movb/movw
>    modes) except EXG,SEX,TFR shaded areas.
>    * Option to offset S12 addresses into XGATE memory space.
>    * Tweak target flags to match other tools. (i.e. -m m68hc11)
>    * Other historical m68hc11/12 changes from Stephane Carrez.
>
> gas/testsuite/ChangeLog
> 2012-03-12  James Murray <jsm@jsm-net.demon.co.uk>
>
>    * gas/m68hc11/insns9s12x.s: New
>    * gas/m68hc11/insns9s12x.d: New
>    * gas/m68hc11/hexprefix.s: New
>    * gas/m68hc11/hexprefix.d: New
>    * gas/m68hc11/9s12x-exg-sex-tfr.s: New
>    * gas/m68hc11/9s12x-exg-sex-tfr.d: New
>    * gas/m68hc11/insns9s12xg.s: New
>    * gas/m68hc11/insns9s12xg.d: New
>    * gas/m68hc11/9s12x-mov.s: New
>    * gas/m68hc11/9s12x-mov.d: New
>    * gas/m68hc11/m68hc11.exp: Updated
>    * gas/m68hc11/*.d: Brought in line with changed objdump output.
>    * gas/all/gas.exp: XFAIL all hc11/12 targets for redef2,3
>    * gas/elf/elf.exp: XFAIL all hc11/12 targets for redef
>
> gas/NEWS
> * Update m68hc11 port. Add support for S12X and XGATE processors
>
> ld/testsuite/ChangeLog
> 2012-03-12  James Murray <jsm@jsm-net.demon.co.uk>
>
>    * ld-m68hc11/xgate-link.s: New
>    * ld-m68hc11/xgate-link.d: New
>    * ld-m68hc11/xgate-offset.s: New
>    * ld-m68hc11/xgate-offset.d: New
>    * ld-m68hc11/xgate1.s: New
>    * ld-m68hc11/xgate1.d: New
>    * ld-m68hc11/xgate2.s: New
>    * ld-m68hc11/m68hc11.exp: Updated
>    * ld-m68hc11/*.d: Brought in line with changed objdump output
>    * ld-gc/gc.exp: Update CFLAGS for m68hc11
>
> ld/NEWS
> * Update m68hc11 port. Add support for S12X and XGATE processors.
>
> opcodes/ChangeLog
> 2012-03-12  James Murray <jsm@jsm-net.demon.co.uk>
>
>    * Add S12X and XGATE co-processor support to m68hc11 target
>     (during period 2008-01 -> 2012-03)
>    * Make objdump output more consistent, use hex instead of decimal
>    and use 0x prefix for hex
>    * Other historical m68hc11/12 changes from Stephane Carrez.
>
> regards
>
> James Murray

  reply	other threads:[~2012-03-12 15:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 22:22 James Murray
2011-03-07 16:35 ` James Murray
2011-03-15  8:33   ` Nick Clifton
2011-03-15 15:08     ` James Murray
2011-12-20 22:20       ` James Murray
2011-12-20 22:29         ` Fred Cooke
2011-12-20 23:23           ` James Murray
2011-12-21 22:29             ` Fred Cooke
2011-12-22 16:52               ` Sean Keys
2011-12-22 17:37               ` James Murray
2012-01-05 22:03                 ` James Murray
2012-01-05 23:11                   ` Fred Cooke
2012-01-10 14:42                   ` nick clifton
2012-01-10 15:45                     ` James Murray
2012-01-12 19:39                       ` 68hc11/12/s12x/xgate patch - style question James Murray
2012-01-12 20:14                         ` Fred Cooke
2012-02-26 23:54                     ` 68hc11/12/s12x/xgate patch James Murray
2012-03-12 15:07                       ` James Murray
2012-03-12 15:26                         ` Fred Cooke [this message]
2012-03-13 20:28                           ` James Murray
2012-03-13 20:56                             ` Fred Cooke
2012-04-02 12:37                         ` James Murray
2012-04-23 17:05                           ` James Murray
     [not found]                             ` <1337003987.27195.60.camel@jsm2>
2012-05-15 12:59                               ` nick clifton
2012-05-15 18:38                                 ` Fred Cooke
2012-05-15 20:26                                 ` James Murray

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='CABZhLO_=6t=8EV5UcKN5LUqz0ZHBjQOqMZQhzNhx2V+HXEmewQ@mail.gmail.com' \
    --to=fred.cooke@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=jsm@jsm-net.demon.co.uk \
    --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).