public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Wolfgang Loidl <hwloidl@informatik.uni-muenchen.de>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: gdb support for m32c?
Date: Thu, 09 Mar 2006 14:41:00 -0000	[thread overview]
Message-ID: <20060309154134.0c08d2e5@anagni.tcs.ifi.lmu.de> (raw)
In-Reply-To: <20060309032449.GA12203@nevyn.them.org>

Hi Daniel,

Thanks for the swift reply. 
I now checked out the HEAD of the gdb cvs rep with the m32c code in
sim. Does "not supported yet" mean that the simulator itself doesn't
work, or just that some GDB features don't work, yet?
As said, at the moment I'd only need the simulator, and I'd happy
with a version even if it's still a bit unstable.

If not, any comments how close that would be to completion? We just
started work on a project that still goes at least 2 years, so we could
plan things around a rough timeplan.

Cheers,
--
 HW

On Wed, 8 Mar 2006 22:24:49 -0500
Daniel Jacobowitz <drow@false.org> wrote:

> On Wed, Mar 08, 2006 at 11:11:33PM +0100, Hans-Wolfgang Loidl wrote:
> > Hi,
> > 
> > The GCC readinglist claims that GDB includes a simulator
> > for the m32c processor.
> > However, downloading the latest gdb snapshot I only found
> > a dir m32r (the RISC rather than CISC version) in the
> > sim/ dir.
> > 
> > Can somebody enlighten me whether GDB does support the
> > m32c, and if so how to include support for it, so that I can
> > at least use it as simulator for GCC generated m32c-elf 
> > binaries.
> 
> The latest CVS version of GDB does include the m32c simulator;
> you may have been looking at an older release branch snapshot.
> However, GDB doesn't yet have an m32c port; I think it got held up in
> review at some point, but I don't remember.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery

  reply	other threads:[~2006-03-09 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 22:11 Hans-Wolfgang Loidl
2006-03-09  3:24 ` Daniel Jacobowitz
2006-03-09 14:41   ` Hans-Wolfgang Loidl [this message]
2006-03-09 15:00     ` Daniel Jacobowitz
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
2006-03-14  2:38   ` DJ Delorie

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=20060309154134.0c08d2e5@anagni.tcs.ifi.lmu.de \
    --to=hwloidl@informatik.uni-muenchen.de \
    --cc=drow@false.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).