RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

Chris Johns chrisj at rtems.org
Wed Aug 14 22:43:11 UTC 2019

On 14/8/19 5:38 pm, Sebastian Huber wrote:
> On 14/08/2019 09:25, Sebastian Huber wrote:
>> On 14/08/2019 09:09, Chris Johns wrote:
>>> On 14/8/19 4:52 pm, Sebastian Huber wrote:
>>>> On 14/08/2019 08:52, Chris Johns wrote:
>>>>>>>> On ARM a breaking change in compiler options is necessary.
>>>>>>> What options are these?
>>>>>> ARM changed the FPU options in GCC 8 and later.
>>>>>>> Also this seems back to front to me. Should all hosts be on 9.2.0 and those
>>>>>>> that
>>>>>>> cannot have specific versions?
>>>>>> Only PowerPC should stay at GCC 7 until the next RTEMS release from my
>>>>>> point of
>>>>>> view. Everything else can move on.
>>>>> Awesome. To make sure I understand the steps ...
>>>>> 1. Move gcc-fb371a33fa6 to 5/rtems-powerpc
>>>>> 2. Set the default to gcc-9.2.0
>>>>> 3. Move all other archs to the defaults
>>>>> ?
>>>> Yes, and:
>>>> 4. Update the ARM BSPs to use the new machine options.
>>> Is there something that documents the changes we need to make?
>> No, you have to compare the multilib configurations in GCC 7 and 9.

I was after something that says change `xxx` to `yyy`. I am happy to do the
change, I do not have the time to figure which options are which.

> Are you looking for information for users of ARM BSPs which have to update their
> hard-coded compiler options? No, we have to provide this information somewhere.

No, users who hard code options into their applications will have to update. We
do not have a way to convey this detail at this point in time, may be a section
in the user manual. My long term wish is to provide a stable interface to RTEMS
that provides these flags.


More information about the devel mailing list