Quote:
Originally Posted by wawa
btw. probably not the case, but if there is anything to get from it, aros uses currently binutils 2.25 for gcc 6.3.0. if needed for reference, the diffs are to find in the usual locations. what id love to see, however likely too much to hope for, would to be bundling effort to improve amiga-m68k backend being usable for both for aros and aos. i lack though the expertise to contribute to it.
|
I wish there were AROS for the m68k, but there isn't. But thank you for pointing it out.
The problems with gcc/binutils are:
1. m68k Amiga register usages: A6 as library base, A5 as frame pointer, A4 as data segment ref.
2. The amiga hunk file format
3. fast ram / chip ram
4. special stuff like resident
5. dunno... guess way more.
The binutils modifications can't be merged easily since many things have changed, but I have an experimental binutils 2.27. And patching binutil 2.14 was easier. (Notice: some bugs I fixed in 2.14 are still present in the current 2.27, so noone really uses that **abandoned** code)
And gcc changed a lot from 3.4.* to 4.0.0. Porting the changes to 4.0.0 is the same effort as porting them to gcc-6, so I started with gcc-6.
Bebbo
PS: I am using the gcc-6 branch, so it's atm "version 6.3.1 20170217 (GCC)"