Re: [RSB 2/4] 6: Update GCC 10 and 12
On 30/6/2023 4:20 pm, Sebastian Huber wrote: > On 29.06.23 02:20, Chris Johns wrote: >> On 28/6/2023 3:33 pm, Sebastian Huber wrote: >>> On 28.06.23 04:37, Chris Johns wrote: Can you please provide something other than update in the commit message? If it is to pick up patches on these gcc release branches then please say so. >>> >>> This update has no particular reason. I just had a bit of time to run my >>> update >>> script. Ideally there would be an automatic update process in place. If you >>> don't want to follow the upstream release branches, then please say so. >>> However, >>> this work helps to identify RTEMS related issues in the upstream >>> development. >>> Working tools for RTEMS need maintenance. It is not that release versions >>> of GCC >>> magically work on RTEMS. >> >> This sounds great. Would it be possible to add a simple comment in the commit >> message this is a housekeeping update to the latest? It makes it easier >> reviewing the commit log to understand changes of interest verses such as >> things >> we need or make in newlib verses housekeeping. > > Ok, makes sense. I added this sentence: > > Keep RTEMS up to date with the upstream development. > Perfect and appreciated. It is now easier to review and accept a change like this. Are these versions of the compiler tracking tarfile packages? >>> >>> No, the configurations track the release branches. >>> >> >> For newlib this makes sense during development and releases because of >> newlib's >> long release period. It also works for binutils, gcc and gdb when we are in >> development however I am not sure it does with releases. Should we look to >> tarfiles for releases for the binutils, gcc and gdb tools? > > For RTEMS releases it makes sense to use upstream releases for the tools with > as > few patches as possible. Great. How do we make the move? I am happy to update the RSB if I am given the details or instructions. I feel you are the best person to know when so if you think it is OK to change does it work if you create a ticket with the links to the sources then assign it to me? Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB 2/4] 6: Update GCC 10 and 12
On 29.06.23 02:20, Chris Johns wrote: On 28/6/2023 3:33 pm, Sebastian Huber wrote: On 28.06.23 04:37, Chris Johns wrote: Can you please provide something other than update in the commit message? If it is to pick up patches on these gcc release branches then please say so. This update has no particular reason. I just had a bit of time to run my update script. Ideally there would be an automatic update process in place. If you don't want to follow the upstream release branches, then please say so. However, this work helps to identify RTEMS related issues in the upstream development. Working tools for RTEMS need maintenance. It is not that release versions of GCC magically work on RTEMS. This sounds great. Would it be possible to add a simple comment in the commit message this is a housekeeping update to the latest? It makes it easier reviewing the commit log to understand changes of interest verses such as things we need or make in newlib verses housekeeping. Ok, makes sense. I added this sentence: Keep RTEMS up to date with the upstream development. Are these versions of the compiler tracking tarfile packages? No, the configurations track the release branches. For newlib this makes sense during development and releases because of newlib's long release period. It also works for binutils, gcc and gdb when we are in development however I am not sure it does with releases. Should we look to tarfiles for releases for the binutils, gcc and gdb tools? For RTEMS releases it makes sense to use upstream releases for the tools with as few patches as possible. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB 2/4] 6: Update GCC 10 and 12
On 28/6/2023 3:33 pm, Sebastian Huber wrote: > On 28.06.23 04:37, Chris Johns wrote: >> Can you please provide something other than update in the commit message? >> >> If it is to pick up patches on these gcc release branches then please say so. > > This update has no particular reason. I just had a bit of time to run my > update > script. Ideally there would be an automatic update process in place. If you > don't want to follow the upstream release branches, then please say so. > However, > this work helps to identify RTEMS related issues in the upstream development. > Working tools for RTEMS need maintenance. It is not that release versions of > GCC > magically work on RTEMS. This sounds great. Would it be possible to add a simple comment in the commit message this is a housekeeping update to the latest? It makes it easier reviewing the commit log to understand changes of interest verses such as things we need or make in newlib verses housekeeping. >> >> Are these versions of the compiler tracking tarfile packages? > > No, the configurations track the release branches. > For newlib this makes sense during development and releases because of newlib's long release period. It also works for binutils, gcc and gdb when we are in development however I am not sure it does with releases. Should we look to tarfiles for releases for the binutils, gcc and gdb tools? Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB 2/4] 6: Update GCC 10 and 12
On 28.06.23 04:37, Chris Johns wrote: Can you please provide something other than update in the commit message? If it is to pick up patches on these gcc release branches then please say so. This update has no particular reason. I just had a bit of time to run my update script. Ideally there would be an automatic update process in place. If you don't want to follow the upstream release branches, then please say so. However, this work helps to identify RTEMS related issues in the upstream development. Working tools for RTEMS need maintenance. It is not that release versions of GCC magically work on RTEMS. Are these versions of the compiler tracking tarfile packages? No, the configurations track the release branches. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [RSB 2/4] 6: Update GCC 10 and 12
Can you please provide something other than update in the commit message?
If it is to pick up patches on these gcc release branches then please say so.
Are these versions of the compiler tracking tarfile packages?
Thanks
Chris
On 27/6/2023 8:21 pm, Sebastian Huber wrote:
> ---
> rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
> rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
> b/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
> index 870c06f..e01542e 100644
> --- a/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
> +++ b/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
> @@ -1,12 +1,12 @@
> %include %{_configdir}/checks.cfg
> %include %{_configdir}/base.cfg
>
> -%define gcc_version 52c451e
> +%define gcc_version ab134ec
> %define gcc_external 1
> %define gcc_expand_name gnu-mirror-gcc-%{gcc_version}
> %source set gcc --rsb-file=%{gcc_expand_name}.tar.gz
> https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/%{gcc_version}
> %hash sha512 %{gcc_expand_name}.tar.gz \
> -
> qjkDEEGK9YmRSSz8sQfwgzy9xPkvcvDNbo68vEM92jAEyVmzbTskJW/MtEyw7hwzOJgjWJsdoMKdsUa0yOXlcw==
> +
> UQEiEegns9qDLBk35p7lrIfeoG3pHOlCPVbnEUqnL3Cqa2yjzl9cc8dNXKUTSvwOeuCQqGN2x08greTe9ZTqaA==
>
> %patch add gcc -p1
> https://devel.rtems.org/raw-attachment/ticket/4196/0001-Back-port-v8-of-gcov-improvements-to-GCC-10.patch
> %hash sha512 0001-Back-port-v8-of-gcov-improvements-to-GCC-10.patch
> c2d1faed68aa0f60bef917365545cc4cc899df428a5d08f178417c06def4fd3cd3a749c1871c8a22552022c29dfae4a3d21161e2b01291e458ea8d670f01887e
> diff --git a/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
> b/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
> index 2277b01..7b0d4cb 100644
> --- a/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
> +++ b/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
> @@ -1,12 +1,12 @@
> %include %{_configdir}/checks.cfg
> %include %{_configdir}/base.cfg
>
> -%define gcc_version efc21f1
> +%define gcc_version 0f54a73
> %define gcc_external 1
> %define gcc_expand_name gnu-mirror-gcc-%{gcc_version}
> %source set gcc --rsb-file=%{gcc_expand_name}.tar.gz
> https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/%{gcc_version}
> %hash sha512 %{gcc_expand_name}.tar.gz \
> -
> KTiGNk2WdP/uwZS8t8L1uy0mwzBjrIIDkD/lZycGyGW9TII7dO//2sRF3jfw1drTOoM6+/bqpkDLp3k1/6TZvA==
> +
> 6q/FCgcnONitGrUuXF9y8nx6FiiSL3JSFwDh31pdJem4QvvcP7pFnybdw/Ve1uOIHab38xZyFVbEsANdAZN6Sg==
>
> %patch add gcc -p1
> https://devel.rtems.org/raw-attachment/ticket/4196/0001-Back-port-v1-of-gcov-tool-merge-stream-to-GCC-12.patch
> %hash sha512 0001-Back-port-v1-of-gcov-tool-merge-stream-to-GCC-12.patch \
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
[RSB 2/4] 6: Update GCC 10 and 12
---
rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
b/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
index 870c06f..e01542e 100644
--- a/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
+++ b/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
@@ -1,12 +1,12 @@
%include %{_configdir}/checks.cfg
%include %{_configdir}/base.cfg
-%define gcc_version 52c451e
+%define gcc_version ab134ec
%define gcc_external 1
%define gcc_expand_name gnu-mirror-gcc-%{gcc_version}
%source set gcc --rsb-file=%{gcc_expand_name}.tar.gz
https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/%{gcc_version}
%hash sha512 %{gcc_expand_name}.tar.gz \
-
qjkDEEGK9YmRSSz8sQfwgzy9xPkvcvDNbo68vEM92jAEyVmzbTskJW/MtEyw7hwzOJgjWJsdoMKdsUa0yOXlcw==
+
UQEiEegns9qDLBk35p7lrIfeoG3pHOlCPVbnEUqnL3Cqa2yjzl9cc8dNXKUTSvwOeuCQqGN2x08greTe9ZTqaA==
%patch add gcc -p1
https://devel.rtems.org/raw-attachment/ticket/4196/0001-Back-port-v8-of-gcov-improvements-to-GCC-10.patch
%hash sha512 0001-Back-port-v8-of-gcov-improvements-to-GCC-10.patch
c2d1faed68aa0f60bef917365545cc4cc899df428a5d08f178417c06def4fd3cd3a749c1871c8a22552022c29dfae4a3d21161e2b01291e458ea8d670f01887e
diff --git a/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
b/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
index 2277b01..7b0d4cb 100644
--- a/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
+++ b/rtems/config/tools/rtems-gcc-12-newlib-head.cfg
@@ -1,12 +1,12 @@
%include %{_configdir}/checks.cfg
%include %{_configdir}/base.cfg
-%define gcc_version efc21f1
+%define gcc_version 0f54a73
%define gcc_external 1
%define gcc_expand_name gnu-mirror-gcc-%{gcc_version}
%source set gcc --rsb-file=%{gcc_expand_name}.tar.gz
https://codeload.github.com/RTEMS/gnu-mirror-gcc/tar.gz/%{gcc_version}
%hash sha512 %{gcc_expand_name}.tar.gz \
-
KTiGNk2WdP/uwZS8t8L1uy0mwzBjrIIDkD/lZycGyGW9TII7dO//2sRF3jfw1drTOoM6+/bqpkDLp3k1/6TZvA==
+
6q/FCgcnONitGrUuXF9y8nx6FiiSL3JSFwDh31pdJem4QvvcP7pFnybdw/Ve1uOIHab38xZyFVbEsANdAZN6Sg==
%patch add gcc -p1
https://devel.rtems.org/raw-attachment/ticket/4196/0001-Back-port-v1-of-gcov-tool-merge-stream-to-GCC-12.patch
%hash sha512 0001-Back-port-v1-of-gcov-tool-merge-stream-to-GCC-12.patch \
--
2.35.3
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
