(First post to gcc mailing list)

I have been making use of the Freescale (Motorola) HC11/12 functionality
within gcc and binutils on the 9S12C64 target. 

I plan to extend gcc to cover the newer S12X CPU as the existing
compiler only utilises the S12 subset. Is anyone working on this
presently?

Hopefully I will be working on this with a colleague Ken Culver and we
would aim to have some code by the middle of the year. I contacted the
existing maintainer of the HC11/12 port Stephane Carrez, but he does not
have the time to actively work on it.
 
Additionally I have extended binutils-2.18 to cope with S12X and the
XGATE co-processor used in chips like the 9S12XD and 9S12XE families. My
code does appear to work but needs a good cleanup and more testing
before it is ready for submission.
( http://www.jsm-net.demon.co.uk/xgate )

I have attempted to build gcc-4.3.0 with --target=m6812-elf and using
plain binutils-2.18 built with the same target, prefix and program
prefix as gcc, however gcc fails:
../../../gcc-4.3.0/libgcc/../gcc/libgcc2.c: In function ‘__negdi2’:
../../../gcc-4.3.0/libgcc/../gcc/libgcc2.c:80: internal compiler error:
Segmentation fault

I believe I have attempted to build it correctly as the same configure
options passed to a gcc-3.3.6 (with Stephane Carrez's patches applied)
builds ok.

My host compiler reports:
[EMAIL PROTECTED] ~]$ gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c
++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-cpu=generic
--host=i386-redhat-linux
Thread model: posix
gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)

regards

James Murray

Reply via email to