Time to bump gcc on master?

[Joel Sherrill]

On Thu, Nov 10, 2016 at 1:36 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> For the libbsd update we need the November Newlib snapshot (or the
> release). I have also a libgomp (OpenMP) performance improvement in the
> queue, for this I need a future GCC snapshot.
>
>
Is the 20161025 snapshot that Jeff just posted OK? We can bump again
when something newer is available.

So gcc 6.2 is not worth the trouble to update to? Are we looking at
a gcc pre-7 snapshot or pre-6.3? Between the new gcc
versioning and the "future GCC snapshot", I am not sure what
you want. GCC makes snapshots about once a week. Which
of these would you be wanting?

ftp://gcc.gnu.org/pub/gcc/snapshots/6-20161103/
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20161106/

With the assumption that we would be moving 4.12 to a released
version as soon as we can.

I am happy to bump the RSB. I just want to make sure I know
where we need to go.

--joel


>
> On 10/11/16 00:44, Joel Sherrill wrote:
>
>> Hi
>>
>> As we approach a 4.12 branching point, we need to pick
>> a better gcc version. The current RTEMS default is
>> gcc-6-20160609
>>
>> I am testing now to bump newlib to newlib-2.4.0.20161025-1.
>>
>> This reports as:
>>
>> sparc-rtems4.12-gcc (GCC) 6.1.1 20160609 (RTEMS 4.12, RSB
>> 6d2eaba6c9bccedc04dfc2802a0d11835a98a417, Newlib 2.4.0.20161025)
>>
>> gcc 6.2 was released in August and based on their new numbering
>> scheme, that should be the release immediately following our
>> snapshot.
>>
>> Anyone have any objections to me updating to gcc 6.2 after
>> seeing how the newlib version bump goes?
>>
>> Thanks.
>>
>> --joel
>>
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20161110/9ac5bbea/attachment-0002.html>