On 2018-10-09 14:59, Sebastian Huber wrote:
On 09/10/2018 14:55, Chris Johns wrote:
On 9/10/18 4:20 am, Sebastian Huber wrote:
I don't have a problem with this patch, but what is the long term
strategy for
Gaisler-specific machine options in GCC and clang? I am pretty sure
this
divergence w
On 09/10/2018 14:55, Chris Johns wrote:
On 9/10/18 4:20 am, Sebastian Huber wrote:
I don't have a problem with this patch, but what is the long term strategy for
Gaisler-specific machine options in GCC and clang? I am pretty sure this
divergence will trouble users at some point.
Can we assume
On 9/10/18 4:20 am, Sebastian Huber wrote:
>
> I don't have a problem with this patch, but what is the long term strategy for
> Gaisler-specific machine options in GCC and clang? I am pretty sure this
> divergence will trouble users at some point.
>
Can we assume there will be all, some or any c
On 09/10/2018 12:37, Daniel Hellstrom wrote:
Module:rtems
Branch:master
Commit:dc32b6aa0807fb70f9b26bc0bc6e164ddb49bd3a
Changeset:http://git.rtems.org/rtems/commit/?id=dc32b6aa0807fb70f9b26bc0bc6e164ddb49bd3a
Author:Daniel Hellstrom
Date: Fri Aug 31 08:21:05 2018 +0200
leon
