public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
To: Nick Clifton <nickc@redhat.com>
Cc: cgen@sources.redhat.com, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: [PATCH] Add new model m32r2 of Renesas M32R.
Date: Thu, 04 Dec 2003 01:34:00 -0000	[thread overview]
Message-ID: <008a01c3ba07$88257740$2569910a@tool.maec.co.jp> (raw)
In-Reply-To: <m3zne93ijy.fsf@redhat.com>

Hi Nick

Thanks!
Kazuhiro

> Hi Kazuhiro-san,
>
> > The attached patches and files add new model m32r2 of Renesas M32R
> > architecture support.
>
> Thank you very much.  I have applied the binutils and cgen specific
> part of your patches along with a couple of changes to the gas
> directory:
>
>   * I made the -error-explicit-parallel-conflicts switch actually
>     generate error messages.
>
>   * I added a -big switch and a .big pseudo op along the lines of the
>     -little switch and .little pseudo op that your patch created.
>
>   * I updated the documentation file gas/doc/c-m32r.texi to document
>     the new support for the M32R2 processor.  I also mentioned the new
>     support in the gas/NEWS file.
>
>   * I made the code that decides if sequential instructions should be
>     converted into parallel instructions use the parallel() function.
>
> The gdb parts of your patches will have to be approved by a GDB
> maintainer.
>
> Cheers
>         Nick
>
> > cgen/ChangeLog
> > 2003-12-02  Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
> >
> >         * cpu/m32r.cpu : Add new model m32r2.
> >         Add new instructions.
> >         Replace occurrences of 'Mitsubishi' with 'Renesas'.
> >         Changed PIPE attr of push from O to OS.
> >         Care for Little-endian of M32R.
> >         * cpu/m32r.opc (CGEN_DIS_HASH, my_print_insn):
> >         Care for Little-endian of M32R.
> >         (parse_slo16): signed extension for value.
> >
> > bfd/ChangeLog
> > 2003-12-02  Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
> >
> >         * archures.c (bfd_mach_m32r2): New machine types.
> >         * cpu-m32r.c : New machine types.
> >         * elf32-m32r.c (m32r_elf_object_p,
m32r_elf_final_write_processing,
> >         m32r_elf_merge_private_bfd_data): New machine types.
> >
> > gas/ChangeLog
> > 2003-12-02  Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
> >
> >         * config/tc-m32r.c : Add new machine m32r2.
> >         Add new instructions.
> >         (line_separator_chars) : Use '!'.
> >         * config/tc-m32r.h : Add new machine m32r2.
> >
> > gas/testsuite/ChangeLog
> > 2003-12-02  Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
> >
> >         * gas/m32r/m32r2.exp : New file for m32r2.
> >         * gas/m32r/m32r2.s : Likewise.
> >         * gas/m32r/m32r2.d : Likewise.
> >
> > include/ChangeLog
> > 2003-12-02   Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
> >
> >         * elf/m32r.h : Add new machine type m32r2 and instruction modes.
>

      parent reply	other threads:[~2003-12-04  1:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 11:04 Kazuhiro Inaoka
2003-12-03 17:45 ` Nick Clifton
2003-12-03 18:39   ` Frank Ch. Eigler
2003-12-04  1:34   ` Kazuhiro Inaoka [this message]

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='008a01c3ba07$88257740$2569910a@tool.maec.co.jp' \
    --to=inaoka.kazuhiro@renesas.com \
    --cc=binutils@sources.redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.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).