Keep RTEMS up to date with the upstream development.
---
rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-10.4-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-13-newlib-head.cfg | 4 ++--
Thanks.
Ask Kinsey some time the weird situation that caught this.
--joel
On Tue, Nov 21, 2023 at 3:05 PM Chris Johns wrote:
> OK to all 3 and thanks
>
> Chris
>
> On 21/11/2023 11:39 pm, Sebastian Huber wrote:
> > Pick up fixes for ARM/optimized-routines and the memory reclamation at
>
OK to all 3 and thanks
Chris
On 21/11/2023 11:39 pm, Sebastian Huber wrote:
> Pick up fixes for ARM/optimized-routines and the memory reclamation at thread
> exit.
>
> Update #4510.
> Update #4967.
> ---
> rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
>
Pick up fixes for ARM/optimized-routines and the memory reclamation at thread
exit.
Update #4510.
Update #4967.
---
rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-10.4-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
On 10.10.23 07:57, Sebastian Huber wrote:
On 09.10.23 23:52, Chris Johns wrote:
Ok to all patches in the series. Thanks for newlib changes for ARM,
they will be nice to use.
I have to fix the riscv issue before we can update Newlib.
I fixed the riscv issue and checked in an updated version
On 09.10.23 23:52, Chris Johns wrote:
Ok to all patches in the series. Thanks for newlib changes for ARM, they
will be nice to use.
I have to fix the riscv issue before we can update Newlib.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email:
On 10.10.23 01:28, Joel Sherrill wrote:
What caused all the recently posted tool build failures?
One issue was that I forgot to remove the
0001-aarch64-Add-ILP32-ABI-support-in-assembly-v2.patch patch.
Another issue is that I have trouble to build the dtc:
make: *** No rule to make target
What caused all the recently posted tool build failures?
On Mon, Oct 9, 2023, 4:52 PM Chris Johns wrote:
> Ok to all patches in the series. Thanks for newlib changes for ARM, they
> will be
> nice to use.
>
> Chris
>
> On 10/10/2023 3:58 am, Sebastian Huber wrote:
> > Pick up latest changes
Ok to all patches in the series. Thanks for newlib changes for ARM, they will be
nice to use.
Chris
On 10/10/2023 3:58 am, Sebastian Huber wrote:
> Pick up latest changes from ARM/optimized-routines.
>
> Close 4510.
> ---
> rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
>
Pick up latest changes from ARM/optimized-routines.
Close 4510.
---
rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-10.4-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-13-newlib-head.cfg
On 21/7/2022 3:21 pm, Sebastian Huber wrote:
> On 20.07.22 22:52, Chris Johns wrote:
>> On 20/7/2022 6:20 pm, Sebastian Huber wrote:
>>> On 20/07/2022 10:11, Chris Johns wrote:
>> Are these TLS allocations in newlib based on a single use of a newlib
>> call
>> that
>> brings in
On 20.07.22 22:52, Chris Johns wrote:
On 20/7/2022 6:20 pm, Sebastian Huber wrote:
On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call that
brings in the reent stuff? How does that work?
No, each TLS object is defined in the
On 20/7/2022 6:20 pm, Sebastian Huber wrote:
> On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call
that
brings in the reent stuff? How does that work?
>>> No, each TLS object is defined in the translation unit which
On 20/07/2022 10:11, Chris Johns wrote:
There seems to be an issue with i386:
08:09:56 runner ['/opt/rtems/6/bin/rtems-ld', '-C',
'/opt/rtems/6/bin/i386-rtems6-gcc', '-c', '-MMD -Wall -Wmissing-prototypes
-Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs
-mtune=pentiumpro
On 20/07/2022 10:11, Chris Johns wrote:
Are these TLS allocations in newlib based on a single use of a newlib call that
brings in the reent stuff? How does that work?
No, each TLS object is defined in the translation unit which uses the object.
The goal is to get only those objects linked in
On 20/7/2022 5:03 pm, Sebastian Huber wrote:
> On 20/07/2022 02:24, Chris Johns wrote:
>> On 19/7/2022 5:18 pm, Sebastian Huber wrote:
>>> On 13/07/2022 11:24, Sebastian Huber wrote:
This makes the --enable-newlib-reent-thread-local
(_REENT_THREAD_LOCAL_STORAGE)
Newlib
On 20/07/2022 02:24, Chris Johns wrote:
On 19/7/2022 5:18 pm, Sebastian Huber wrote:
On 13/07/2022 11:24, Sebastian Huber wrote:
This makes the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE)
Newlib configuration option available.
Any comments with respect to using the
On 19/7/2022 5:18 pm, Sebastian Huber wrote:
> On 13/07/2022 11:24, Sebastian Huber wrote:
>> This makes the --enable-newlib-reent-thread-local
>> (_REENT_THREAD_LOCAL_STORAGE)
>> Newlib configuration option available.
>
> Any comments with respect to using the Newlib thread-local storage
>
On 13/07/2022 11:24, Sebastian Huber wrote:
This makes the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE)
Newlib configuration option available.
Any comments with respect to using the Newlib thread-local storage
configuration option for arm, i386, microblaze, nios2, powerpc,
This makes the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE)
Newlib configuration option available.
Update #4560.
---
.../config/tools/rtems-gcc-10-newlib-head.cfg | 4 +--
.../tools/rtems-gcc-10.4-newlib-ea99f21.cfg | 27 +++
20 matches
Mail list logo
