68HC11&68HC12 port for Binutils, Gdb and Gcc

68HC11&68HC12 port for Binutils, Gdb and Gcc

[Stephane Carrez]

Hi Binutils, Gdb, Gcc maintainers, and co,

At beginning of 1999, I've started to port the Binutils, Gdb and Gcc
for the Motorola 68HC11 and 68HC12 microcontrollers. The full port 
is completely operational for a long time now.

I took quite a lot of time to validate it, fix bugs and polish the code.
Too much time would say the ones that whished to have all this
integrated in FSF mainline source trees. However, throught this
long and slow process I've been able to make sure the port is correct
and the directions I took are the good ones.

I was also concerned by trying to limit the number of patches I will submit
to binutils, gdb and gcc mailing lists. I know that some maintainers are 
overwhelmed by patches and it was of no use to send them half working port.

But now is the time for patches.

In the following weeks, I will send a number of patches:

 - to binutils for the support of 68HC11 and 68HC12 in bfd, opcodes,
   gas and ld. This will include a validation suite for the assembler.   

 - to gdb for the 68HC11 support and for a 68HC11 simulator (with SCI, 
   SPI, eeprom, nvram, timer devices). This will include some fixes
   to the current simulator support.

 - to gcc for the 68HC11 and 68HC12 code generation including some
   fixes and a couple of improvements.

To validate the port, I ported newlib 1.8.2 and I setup some dejagnu files.
(I've obtained 46 failures on 16008 tests for gcc 2.95, and 124 failures
 on 19424 tests for gcc 2.96, CVS of June 10)

I have a letter of assignment for binutils, gdb and gcc but I have none for
newlib and dejagnu. I can still send you the patches for newlib and dejagnu
if you like. (available on the web anyway).

That's all folks, I hope you'll be prepared to receive the patches,

Thanks,
	Stephane
 
-----------------------------------------------------------------------
         Home                               Office
E-mail: stcarrez@worldnet.fr               Stephane.Carrez@sun.com
WWW:    http://home.worldnet.fr/stcarrez   http://www.sun.com
Mail:   17, rue Foucher Lepelletier        6, avenue Gustave Eiffel
        92130 Issy Les Moulineaux          78182 Saint Quentin en Yvelines
        France

Re: 68HC11&68HC12 port for Binutils, Gdb and Gcc

[Kevin Buettner]

On Jun 17, 12:06am, Stephane Carrez wrote:

> Hi Binutils, Gdb, Gcc maintainers, and co,
> 
> At beginning of 1999, I've started to port the Binutils, Gdb and Gcc
> for the Motorola 68HC11 and 68HC12 microcontrollers. The full port 
> is completely operational for a long time now.

[...]

> I have a letter of assignment for binutils, gdb and gcc but I have none for
> newlib and dejagnu. I can still send you the patches for newlib and dejagnu
> if you like. (available on the web anyway).
> 
> That's all folks, I hope you'll be prepared to receive the patches,

Hi Stephane,

I looked over the gdb portions of your patches that I found at

  http://home.worldnet.fr/~stcarrez/snapshots/gdb-4.18-m68hc11-20000416.diffs.gz

Overall, the patches look good.  Some comments...

 - Send your gdb patches to gdb-patches@sourceware.cygnus.com.

 - When you send us your patches, don't include patches for ChangeLog
   comments.  Instead, prepend your ChangeLog entries to the front of
   the patch.  The person integrating your patch will put them in the
   ChangeLog just prior to committing them.

 - Don't send patches for the configure scripts (or any other files
   which are automatically generated.)  We do need patches for 
   configure.in though.  (I understand why they're in the patch on your
   web page though.)

 - It'd be best if you'd generate your patches with respect the latest
   development sources.  For gdb, information on accessing the CVS
   repository may be found at

	http://sourceware.cygnus.com/gdb/#download

   This will involve a bit of work on your part since it is quite likely
   that your 4.18 patches will not apply cleanly to the current source
   base.  However, you really are the best one to do this work since
   you are the one most familiar with your port and you also have the
   equipment to test the end result.

 - Over time, it would be best if you'd "multi-arch" your target.  This
   means that most of the stuff defined via macros in tm-m68hc11.h
   will get moved to m68hc11-tdep.c and will be defined as functions
   instead.  You will also add m68hc11_gdbarch_init() (or somesuch) to
   your tdep.c file to set up access to these functions through the
   multi-arch framework.  For examples of multi-arched code, take a
   look at d10v-tdep.c, mips-tdep.c, or ia64-tdep.c.

   I think it'd be okay though if you'd submit your code in it's
   present non-multiarched form, get it into the repository, and then
   work on multi-arching it.  (We can help you with that, but it'll be
   easier if your code is in place first.)

 - I noticed that support for calling inferior functions (all of the
   call dummy stuff) isn't finished yet.  That's okay...  but when you
   get around to it, I suggest you use the generic dummy frames
   machinery.  (You will be amazed at how much easier this is to use
   than the old mechanism.) Search for the "GENERIC DUMMY FRAMES"
   comment in blockframe.c for more information.

Kevin