[RSB PATCH] 6: Merge the MacOS M silicon patch from gcc-12 to gcc-13

[Cedric Berger]

Hello,

On 18.12.2023 07:05, Chris Johns wrote:
> On 16/12/2023 2:04 am, Cedric Berger wrote:
>> Hello Heinz,
>>
>> On 15.12.2023 10:44, Heinz Junkes wrote:
>>> HI,
>>> I can follow Cedric's reasoning. Even if I was the initiator of this discussion.
>>>
>>> I use RTEMS in my lectures/exercises, among other things, and have always been
>>> able to give the students
>>> freedom which laptops with which OS they wanted to use. And there are many of
>>> them with used
>>> older laptops. Intel Macs, for example.
>>>
>>> But you can also use a VM with Linux on all these systems.
>>>
>>> It might then be okay to communicate openly that there will be no more support
>>> for Macs in the future.
>> Just to be clear: I'm not advocating dropping Mac support, just dropping the
>> support for the old intel-based ones (the ones with issues right now).
>>
>> Mac with M1/M2/M3 work fine with the latest tooling.
> I think there is a middle ground here and that means some investigation is
> needed to determine what works and what is at issue then deciding how much
> further work is done. I have done some of this. The results are based on what I
> have working:
>
> Builds:
>
>    Sonoma

Well, if it works on Sonoma (the latest MacOS version), then IMO that's 
all that matter.

So if the middle ground is to only support the latest MacOS version 
(when RTEMS 6.0 is released) I think this is totally reasonnable.

It is true that the first iterations of a new MacOS release (14.0, 14.1) 
is often buggy, and then gets stabilised around the .2 version, but 
we're past that now.

Cedric

>    Montery
>    Big Sur
>
> Fails:
>
>    Ventura
>
> The failure on Ventura is in GMP called from MPFR. Running the GMP tests a
> number fail and removing --disable-shared improves the test results but GCC does
> not build. I have not looked any further.
>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20231219/1330aec2/attachment.htm>