Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <jmiguelbenitez@supercable.es>
To: <gdb@sources.redhat.com>
Subject: Re: Re: mcore-*-* target to be deleted?
Date: Mon, 13 Dec 2004 12:59:00 -0000	[thread overview]
Message-ID: <20041213125940.NFCK6734.smtp05.retemail.es@smtp05> (raw)

> 
> The mcore code has, unfortunatly, become very out of date.   The 
> mainline hasn't built since 6.2 was released, and with 6.3 past that 
> broken code was dropped.  This all came about because GDB's frame code 
> was rewritten from scratch and the mcore was never updated to work with 
> the new code.
> 
> The way to revive the mcore isn't through votes, nominations, or 
> appointments, it's through code.  A developer with an assignment 
> contributes code to current standards (most importantly does not use 
> deprecated interfaces) then it can very easily be re-integrated (and 
> they may quickly find themselves in a more responsible role).  Any 
> questions on how to do it welcome(1).
> 
> Andrew
> 
> (1) Exprerience suggests that largely starting from scratch (using the 
> existing code as a guideline) is easier.  This is because the bulk of 
> the current file is redundant.
> 

Hi,

I´m doing some academical research on mcore simulator and I briefly studied the sources for mcore simulator. Is that enough to be the new maintainer? I´m not up to date with changes in the simulator interface, but I could work with that.

Jose Miguel Benitez



             reply	other threads:[~2004-12-13 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 12:59 jmiguelbenitez [this message]
2004-12-16  8:35 jmiguelbenitez
2004-12-17  8:19 jmiguelbenitez

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=20041213125940.NFCK6734.smtp05.retemail.es@smtp05 \
    --to=jmiguelbenitez@supercable.es \
    --cc=gdb@sources.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