are we talking GCC for MiNT or GCC for Atari ST, of GCC for m68K.
any m68020-60 target includes most CPU upgrades.
if there was a an 030 soft-float then that might make it easier to do
tests on Hatari's Falcon Compatibility.
as for the patches that Mikro just supplied, are they of interest to
the Amiga and Mac communities?
remember this is Atari ST, and we are stuck with:
68000
68020
68030
68030+FPU
68040
68060
m5475
there is a reason its called "mulit-lib", bite the bullet Mikro, it
will do us all better in the long run, even if it means more work now.
Automation of builds will help in the near future too, so dont be
afraid :)
Has anyone considered 68080 as well?
Paul
On 10/4/18, Miro Kropáček <mir...@gm...> wrote:
> On Wed, 3 Oct 2018 at 21:31, Vincent Rivière <vin...@fr...>
> wrote:
>
>> It is supposed to allow a new m68020-60 target without FPU to GCC.
>> Namely:
>> m68020-60/msoft-float
>> m68020-60/mshort/msoft-float
>>
>> Do you think it is a good thing to officially adopt this change?
>> This will allow to build software optimized for plain Falcon without FPU.
>>
> See my previous email. m68020-60 is a thing of the past, we shouldn't be
> taking it even further and extend it, IMHO. Plus what m68020-60/msoft-float
> really is? No FPU, no 64-bit mul/div, ... it's far more straightforward
> just to use -m68000.
>
> The new (well, new - it has been here since 2007) gcc m68k framework is
> focused on cpus / archs only, so any custom options are destined to be on
> the second level (like /usr/lib/cpu/custom_option, for instance
> /usr/lib/m68020/msoft-float).
>
> Accidentally I have been thinking about this issue too recently but
> couldn't come up with anything better than multiple targets. Trouble is
> that on Atari we are used to have one 020+ binary, somewhat tolerating only
> the requirement of an FPU (emulated or real). When cutting m68020-60 off,
> we immediately get several incompatible replacements:
>
> - m68020 uses 32x32=64 multiplication (and a few others, making it
> incompatible with 040/060)
> - m68040 uses move16 (making it incompatible with 020/030) and various
> instructions present on 020/030/040 but emulated on 060 (movep, mul/div
> mentioned above, even some FPU instructions)
> - m68060 uses move16 (making it incompatible with 020/030)
>
> So maybe we should just add m68020/msoft-float for Falcon without FPU and
> keep the rest as is, I don't know.
>
> --
> MiKRO / Mystic Bytes
> http://mikro.atari.org
>
|
