From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2535 invoked by alias); 16 Dec 2004 08:35:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2318 invoked from network); 16 Dec 2004 08:35:45 -0000 Received: from unknown (HELO smtp09.retemail.es) (62.81.186.19) by sourceware.org with SMTP; 16 Dec 2004 08:35:45 -0000 Received: from smtp09 ([172.20.125.134]) by smtp09.retemail.es (InterMail vM.6.01.03.05 201-2131-111-107-20040910) with SMTP id <20041216083544.BKZH26937.smtp09.retemail.es@smtp09> for ; Thu, 16 Dec 2004 09:35:44 +0100 From: To: Subject: Re: Re: mcore-*-* target to be deleted? Date: Thu, 16 Dec 2004 08:35:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20041216083544.BKZH26937.smtp09.retemail.es@smtp09> X-SW-Source: 2004-12/txt/msg00093.txt.bz2 > > > > 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 > Hi again! Maybe my mail was too short and too mysterious (sorry for my gramatical mistakes!), but I have problems with my personal computer and I must check my mail while I'm working, so I cannot spend too much time. As I said, I'm working with the mcore simulator. Even I made changes to the sources modifying memory management and trying to include some peripherals. As a result of that work, I got familiarized with the gdb simulator interface and with the sources for mcore. So I think I´m able to study the new changes in the interface and to adapt the mcore sources (I guess). Also I want to participate in SL community and I feel like working with gdb. I am a telecommunications engineer and I've experience in C programming. I don't know if all this is enough, but I'm ready for hard work. I hope you consider my offering. Thanks and greetings!