On 05/07/2020 17:27, Joel Sherrill wrote:
> Since the new build system will be a hard break, maybe we should
keep the
> options as is in the old build system and start with the new
options in the new
> build system.
This seems reasonable.
And how will we know which cha
On Sat, Jul 4, 2020, 10:20 PM Chris Johns wrote:
> On 4/7/20 5:43 pm, Sebastian Huber wrote:
> > On 04/07/2020 01:03, Chris Johns wrote:
> >> On 3/7/20 5:06 pm, Sebastian Huber wrote:
> >>> Hello,
> >>> someone from ARM changed the machine options used to build the RTEMS
> multilibs
> >>> some ti
On 4/7/20 5:43 pm, Sebastian Huber wrote:
> On 04/07/2020 01:03, Chris Johns wrote:
>> On 3/7/20 5:06 pm, Sebastian Huber wrote:
>>> Hello,
>>> someone from ARM changed the machine options used to build the RTEMS
>>> multilibs
>>> some time ago (I think GCC 8):
>> Was a reason given?
> ARM thinks
On 04/07/2020 01:03, Chris Johns wrote:
On 3/7/20 5:06 pm, Sebastian Huber wrote:
Hello,
someone from ARM changed the machine options used to build the RTEMS multilibs
some time ago (I think GCC 8):
Was a reason given?
ARM thinks the new options are easier to use.
arm-rtems6-gcc -print-mu
On 3/7/20 5:06 pm, Sebastian Huber wrote:
> Hello,
>
> someone from ARM changed the machine options used to build the RTEMS multilibs
> some time ago (I think GCC 8):
Was a reason given?
>
> arm-rtems6-gcc -print-multi-lib -march=armv4t
> .;
> thumb;@mthumb
> armv5te+fp/hard;@march=armv5te+fp@m
On Fri, Jul 3, 2020 at 2:06 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello,
>
> someone from ARM changed the machine options used to build the RTEMS
> multilibs some time ago (I think GCC 8):
>
> arm-rtems6-gcc -print-multi-lib -march=armv4t
> .;
> thumb;@mthumb
> armv5te+
Hello,
someone from ARM changed the machine options used to build the RTEMS
multilibs some time ago (I think GCC 8):
arm-rtems6-gcc -print-multi-lib -march=armv4t
.;
thumb;@mthumb
armv5te+fp/hard;@march=armv5te+fp@mfloat-abi=hard
thumb/armv6-m;@mthumb@march=armv6-m
thumb/armv7-a;@mthumb@march=
