[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] GCC 4.4.0 for ColdFire
On Fri, 2009-06-05 at 01:49 +0200, Vincent Rivière wrote:
> I have updated GCC 4.4.0 for full ColdFire support :-)
> The patches and Cygwin binaries are available at the usual place:
> I have included all the ColdFire libraries, including MiNTLib, PML (too lazy
> to switch to fdlibm), and GEMLib. It means that any TOS or GEM program
> written in C or C++ can be compiled for ColdFire. The resulting executable
> will run exclusively on ColdFire machines, at full speed, without any emulation.
> In order to switch on ColdFire compilation, you just have to add the option
> -mcpu=5475 to the gcc command line. That's all ! You could use any other V4e
> CPU option, from 5470 to 5485, the result would be the same. The option
> -mcfv4e still works, but it is deprecated.
> In order to follow GCC standards, I renamed the V4e multilib directory to
> m5475 (instead of mcfv4e in the previous version).
> Beware to NOT link with the -g option, because it will use libc_g.a instead
> of m5475/libc.a, so the executable will contain unoptimized 68000 code and
> will fail on a pure ColdFire system (without emulation). The same issue with
> -g occurs when compiling with -m68020-60. To be sure of what gets linked
> into your executable, I recommend to link with the -Wl,-t option to see the
> list of all the object files with their full path.
> ColdFire binaries are mostly useless now, but they will be useful for the
> developers of the new ACP project. However, you can try right now to compile
> your own software for ColdFire in order to check the compatibility with the
> ColdFire. Your programs will run at the highest speed on the upcoming ACP
> computer !
Very useful for me Vincent. I'll start Gentoo on Coldfire soon.
I'd love to get your binutils & gcc patches upstream.
Can we start that process and let us know the bug submission ID's ??
Thanks Vincent for this excellent work!