From: Daniel Jacobowitz <drow@false.org>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sourceware.org, hwloidl@informatik.uni-muenchen.de
Subject: Re: gdb support for m32c?
Date: Tue, 14 Mar 2006 02:23:00 -0000 [thread overview]
Message-ID: <20060314022350.GA1097@nevyn.them.org> (raw)
In-Reply-To: <200603102130.k2ALUJ3M004786@greed.delorie.com>
On Fri, Mar 10, 2006 at 04:30:19PM -0500, DJ Delorie wrote:
> Alas, it needs some patches, although they're minor. I use the
> simulator a LOT so it's fairly stable.
>
> I missed that the m32c sim had been approved. I'm supposed to be the
> m32c sim maintainer but Jim didn't add me as part of the commit
> process. How to proceed?
I don't know. I vaguely remember this coming up when the patch was
submitted; ah, there was some confusion about whether there was already
an m32c port and it was already yours. If you want maintainership of
this sim, I don't think anyone will object; could you add yourself to
sim/MAINTAINERS?
> Also, while I can get the simulator to build, it currently doesn't get
> that far because it has a dependency on gdb being at least configured,
> which doesn't happen yet. That's why I didn't notice my builds
> suddenly including the simulator :-P
It'd be nice to get the GDB port finalized, one way or another.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-14 2:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 21:30 DJ Delorie
2006-03-10 22:45 ` Hans-Wolfgang Loidl
2006-03-10 22:55 ` DJ Delorie
2006-03-10 23:12 ` Hans-Wolfgang Loidl
2006-03-10 23:21 ` DJ Delorie
2006-03-14 2:23 ` Daniel Jacobowitz [this message]
2006-03-14 2:38 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 22:11 Hans-Wolfgang Loidl
2006-03-09 3:24 ` Daniel Jacobowitz
2006-03-09 14:41 ` Hans-Wolfgang Loidl
2006-03-09 15:00 ` Daniel Jacobowitz
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=20060314022350.GA1097@nevyn.them.org \
--to=drow@false.org \
--cc=dj@redhat.com \
--cc=gdb@sourceware.org \
--cc=hwloidl@informatik.uni-muenchen.de \
/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).