This is the mail archive of the gdb-patches@sourceware.cygnus.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ARM Linux port...



   Sender: scottb@cygnus.com
   Date: Wed, 12 May 1999 15:13:29 -0400

   I've been working on the ARM Linux port of GDB 4.18 for the NetWinder lately.  I
   have reached the point where all the mechanics are satisfied.  (ie: I have host,
   target and native files, it configures etc).  I can now concentrate on what is
   required for the actual port.

Great!

   The last time I did this (for 4.17 a year ago), I split the existing ARM files
   into two parts.  One was common code for both the linux and riscix targets, and
   the other specific to riscix.  I then added files specific to ARM linux complete
   my port.  I would like to do the same again, (there is no point reinventing the
   wheel) and will do so if there are no objections.  I'm not sure who maintains
   this code, (someone has as it has changed since 4.17), but if they could contact
   me perhaps we could work together to make such a move as painless as possible.

Elena Zannoni (ezannoni@cygnus.com) is responsible for generic ARM
bits, but since there's no existing ARM Linux port, I usually get the
task of looking at new stuff, and signing up someone like yourself :-)
to be its maintainer.  I'm going to be on vacation for two weeks starting
on the 17th, so if you want quick feedback, send the patches now!

   At the same time, I prefer writing ANSI style C, and there have been discussions
   about moving the GDB code to this style.  Should I make this stylistic change,
   and submit my patches?  I don't want to be in the position where I have my
   changes rejected for stylistic reasons.

It's currently OK to use pure ANSI for files that you know will never
be seen by an old compiler - so for instance ARM Linux native code
could be ANSI if you wanted.  It's been a month since the 4.18
release, with no complaints so far, and when a couple of weeks ago I
proposed end of June as the decision point, I didn't get any
objections.  So if you're keen to get patches in before then, then K&R
compat is required, but if you'd rather wait, that's OK too.  It may
be that discussion of the patches will take 6 weeks... :-)

							Stan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]