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
