Re: [uClinux-dev] [PATCH v2 1/6] m68k: merge mmu and non-mmu versions of muldi3

[Philippe De Muyter <phdm@macqel.be>]

Hi Greg,

On Wed, Apr 20, 2011 at 09:01:39PM +1000, Greg Ungerer wrote:
> Hi Philippe,
>
> On 20/04/11 20:38, Philippe De Muyter wrote:
>> Hi Greg,
>>
>> On Wed, Apr 20, 2011 at 08:18:09PM +1000, Greg Ungerer wrote:
>>>>
>>>> The 68340 has it also. (And I have an old linux port for this processor)
>>>
>>> That is just a SoC that contains a 68020 though, so __mc68020__ would
>>> be defined for that.
>>
>> No, this is a cpu32 core, which is a subset of a 68020, so gcc does not
>> define __mc68020__, or at least should not (there are old bug reports
>> about that).
>
> Modern gcc still does, from a gcc-4.5.1:
>
> # m68k-linux-gcc -mcpu32 -dM -E - < /dev/null | grep mc68020
> #define __mc68020__ 1
> #define __mc68020 1
> #define mc68020 1
>
>
>>>> I surmise the 68360 has it also.
>>>
>>> I believe that is a SoC with a 68040 cpu core, so I would expect that
>>> __mc68040__ would be correct for that.
>>
>> This is a cpu32+ core.
>>
>> Same here.
>>
>> Not that it is that important now :)
>
> Does cpu32 always support the 64bit mul?

Yes AFAIK.

> If so we can just add __mcpu32__ to the conditional check list.

That would be safer.

Thanks

Philippe