Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Sebastian Huber
On 21.07.22 10:36, Chris Johns wrote: On 21/7/2022 6:30 pm, Sebastian Huber wrote: On 21.07.22 10:27, Chris Johns wrote: On 21/7/2022 6:21 pm, Sebastian Huber wrote: On 21.07.22 10:16, Chris Johns wrote: On 21/7/2022 6:11 pm, Sebastian Huber wrote: On 21.07.22 10:03, Chris Johns wrote:

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Chris Johns
On 21/7/2022 6:30 pm, Sebastian Huber wrote: > On 21.07.22 10:27, Chris Johns wrote: >> On 21/7/2022 6:21 pm, Sebastian Huber wrote: >>> On 21.07.22 10:16, Chris Johns wrote: On 21/7/2022 6:11 pm, Sebastian Huber wrote: > On 21.07.22 10:03, Chris Johns wrote: >> As an aside, does gdb

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Sebastian Huber
On 21.07.22 10:27, Chris Johns wrote: On 21/7/2022 6:21 pm, Sebastian Huber wrote: On 21.07.22 10:16, Chris Johns wrote: On 21/7/2022 6:11 pm, Sebastian Huber wrote: On 21.07.22 10:03, Chris Johns wrote: As an aside, does gdb know about TLS variables and so will `errno` be visible? Good

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Chris Johns
On 21/7/2022 6:21 pm, Sebastian Huber wrote: > On 21.07.22 10:16, Chris Johns wrote: >> On 21/7/2022 6:11 pm, Sebastian Huber wrote: >>> On 21.07.22 10:03, Chris Johns wrote: As an aside, does gdb know about TLS variables and so will `errno` be visible? >>> Good question, there seems to

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Sebastian Huber
On 21.07.22 10:16, Chris Johns wrote: On 21/7/2022 6:11 pm, Sebastian Huber wrote: On 21.07.22 10:03, Chris Johns wrote: As an aside, does gdb know about TLS variables and so will `errno` be visible? Good question, there seems to be some support missing. For example for

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Chris Johns
On 21/7/2022 6:11 pm, Sebastian Huber wrote: > On 21.07.22 10:03, Chris Johns wrote: >> As an aside, does gdb know about TLS variables and so will `errno` be >> visible? > > Good question, there seems to be some support missing. For example for > arm/xilinx_zynq_a9_qemu: > > Breakpoint 7, Init

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Sebastian Huber
On 21.07.22 10:03, Chris Johns wrote: As an aside, does gdb know about TLS variables and so will `errno` be visible? Good question, there seems to be some support missing. For example for arm/xilinx_zynq_a9_qemu: Breakpoint 7, Init (ignored=2118804) at

Re: [PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Chris Johns
+1 Really great patch and change. I think the performance improvements will be excellent. As an aside, does gdb know about TLS variables and so will `errno` be visible? Chris On 21/7/2022 5:09 pm, Sebastian Huber wrote: > This patch set adds support for the --enable-newlib-reent-thread-local >

[PATCH v2 0/3] Support --enable-newlib-reent-thread-local Newlib configuration option

2022-07-21 Thread Sebastian Huber
This patch set adds support for the --enable-newlib-reent-thread-local (_REENT_THREAD_LOCAL_STORAGE) Newlib configuration option. By default, Newlib uses a huge object of type struct _reent to store thread-specific data. This object is returned by __getreent() if the __DYNAMIC_REENT__ Newlib