From: Joel Brobecker <brobecker@adacore.com>
To: Michael Eager <eager@eagercon.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Support for Xilinx MicroBlaze architecture (1 of 3)
Date: Mon, 14 Sep 2009 17:04:00 -0000 [thread overview]
Message-ID: <20090914170359.GI8327@adacore.com> (raw)
In-Reply-To: <4AAAA1CF.6080403@eagercon.com>
Michael,
> 2009-09-11 Michael Eager <eager@eagercon.com>
>
> * configure.tgt: Add targets microblaze*-linux-*, microblaze*-xilinx-*.
> * doc/gdb.texinfo: Add MicroBlaze.
> * MAINTAINERS: Add self as maintainer for MicroBlaze.
> * Makefile.in: Build microblaze-tdep.o, microblaze-linux-tdep.o.
> * microblaze-linux-tdep.c: New.
> * microblaze-rom.c: New.
> * microblaze-tdep.c: New.
> * microblaze-tdep.h: New.
I will look at this part.
> * opcodes/microblaze-dis.c: Rewrite.
> * opcodes/microblaze-opc.h: Rewrite.
> * opcodes/microblaze-opcm.h: Rewrite.
This part is maintained by binutils. Can you send the patch there?
> * sim/configure.ac: Add target microblaze-*-*.
> * sim/configure: Regenerate.
> * sim/microblaze/config.in: New.
> * sim/microblaze/configure.ac: New.
> * sim/microblaze/configure: Generate.
> * sim/microblaze/interp.c: New.
> * sim/microblaze/Makefile.in: New.
> * sim/microblaze/microblaze.h: New.
> * sim/microblaze/microblaze.isa: New.
> * sim/microblaze/sim-main.h: New.
> * sim/microblaze/sysdep.h: New.
This part should be independent from the GDB part. Can you separate
it out and copy Ben Elliston and Frank Ch. Eigler, asking them for
review?
Thanks,
--
Joel
next prev parent reply other threads:[~2009-09-14 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 19:15 Michael Eager
2009-09-12 8:47 ` Eli Zaretskii
2009-09-12 18:35 ` Michael Eager
2009-09-12 19:36 ` Eli Zaretskii
2009-09-12 8:49 ` Eli Zaretskii
2009-09-12 18:36 ` Michael Eager
2009-09-14 17:04 ` Joel Brobecker [this message]
2009-09-14 17:29 ` Michael Eager
2009-09-14 17:34 ` Joel Brobecker
2009-09-14 17:39 ` Michael Eager
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=20090914170359.GI8327@adacore.com \
--to=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
/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