Release 3.0.1 is available

Release 3.0.1 of the GNU Development Chain for 68HC11/68HC12 is available. It is based on Binutils 2.15, Gcc 3.3.5, Gdb 6.2 and Newlib 1.12.0.

It is available as source and binary for GNU/Linux and Windows.

It contains the following fixes and improvements:

Gcc
* Fix [bug #11813] Code generation problem (bset/bclr -m68hc12 -Os
indirect addr)
* Fix [bug #12243] Loop compiles incorrectly (HC12)
* Fix [bug #12297] -fomit-frame-pointer and -Os generate wrong code on
the HCS12
* Fix [bug #12572] internal compiler error; unsigned short in for loop

This is available on the following sites:

http://m68hc11.serveftp.org/m68hc11_port.php
http://www.gnu-m68hc11.org

and also on anonymous ftp server:

ftp://m68hc11.serveftp.org/pub/m68hc11/gnu

Please, file any bug report on http://savannah.gnu.org/bugs/?group=m68hc11

Enjoy and have fun,

Stephane

Compiling GNU C in MAC OS X

Hi all:

I was trying to compile the GNU C Release 3.1. But, I got an error messages like the following:

larith.asm:39:Unknown pseudo-op: .mode
larith.asm:39:Rest of line ignored. 1st junk character valued 109 (m).
larith.asm:41:Unknown pseudo-op: .mode
larith.asm:41:Rest of line ignored. 1st junk character valued 109 (m).
larith.asm:unknown:file contains unmatched .macro and .endmacro for: declare_nearname

I even applied the patches before I compiled in MAC OS X environment.

Any idea how to fix it?

Thanks in advance,

-John

Compiling GNU C in MAC OS X

I think it's the Apple's assembler (installed in /usr/libexec/gcc/darwin/ppc/as) don't understand larith.asm, or the options, I also get:

/usr/libexec/gcc/darwin/ppc/as: I don't understand 'm' flag!
/usr/libexec/gcc/darwin/ppc/as: I don't understand '6' flag!
/usr/libexec/gcc/darwin/ppc/as: I don't understand '8' flag!
/usr/libexec/gcc/darwin/ppc/as: I don't understand 'h' flag!
/usr/libexec/gcc/darwin/ppc/as: I don't understand 'c' flag!
/usr/libexec/gcc/darwin/ppc/as: I don't understand '1' flag!

before the larith.asm errors

Sorry, the reason for the

Sorry, the reason for the use of Apple's as was because the make of binutils-2.15 fail to create the m6811-elf-as.
Anyway the reason binutils-2.15 fails is for the patch, without the patch works OK, by the way the link to 'Why patching?' is broken.