[PATCH] score: Fix TLS support for some code models

Store symbols with an arbitrary absolute address such as _TLS_Size, _TLS_Alignment, _TLS_Data_size, and _TLS_BSS_size in an object to avoid issues with some code models. Update #4953. --- cpukit/include/rtems/score/tls.h | 120 +- cpukit/score/src/tlsallocsize.c |

[rtems-tools PATCH v2] linker: Add TLS support to the symbol table generator

From: Chris Johns Updates #4920 --- linkers/rtems-syms.cpp | 179 ++--- 1 file changed, 134 insertions(+), 45 deletions(-) diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp index e5170e1..c72ee55 100644 --- a/linkers/rtems-syms.cpp +++ b/linkers/rt

[rtems-tools PATCH] linker: Add TLS support to the symbol table generator

From: Chris Johns This is not complete as it has aarch64 code that should be in the kernel. --- linkers/rtems-syms.cpp | 179 ++--- 1 file changed, 134 insertions(+), 45 deletions(-) diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp index e5170e1..

Re: [gcc] Enable TLS support for RTEMS in libstdc++

08/06/2022 15:39, Joel Sherrill wrote: >>> > Is TLS actually supported on all targets except MIPS? >>> >>>     I only added MIPS since this target has a fundamental issue with the >>>     TLS >>>     support. >

Re: [gcc] Enable TLS support for RTEMS in libstdc++

> >>> <mailto:sebastian.hu...@embedded-brains.de>> wrote: > >>> > >>> On 08/06/2022 15:39, Joel Sherrill wrote: > >>> > Is TLS actually supported on all targets except MIPS? > >>> > >>> I only added MIPS since

Re: [gcc] Enable TLS support for RTEMS in libstdc++

t; >>>     On 08/06/2022 15:39, Joel Sherrill wrote: >>> > Is TLS actually supported on all targets except MIPS? >>> >>>     I only added MIPS since this target has a fundamental issue with the >>>     TLS >>>     support. >>>

Re: [gcc] Enable TLS support for RTEMS in libstdc++

except MIPS?     I only added MIPS since this target has a fundamental issue with the     TLS     support.     Which target would you also exclude? About half of them. It seems to be only bfin, lm32, moxie, or1k, and v850. Are these targets still in use? Do we have a maintainer for these ta

Re: [gcc] Enable TLS support for RTEMS in libstdc++

iw no POSIX keys. After I added 2 POSIX keys the test failed as I expected it to. Currently there is no way to check or inform a user the POSIX key create as failed. I think there is a gcc ticket on this topic I raised a while ago. FWIW Jonathan Wakely has a fix for the issue I am seeing with the

Re: [gcc] Enable TLS support for RTEMS in libstdc++

s target has a fundamental issue with the TLS support. Which target would you also exclude? About half of them. It seems to be only bfin, lm32, moxie, or1k, and v850. Are these targets still in use? Do we have a maintainer for these targets? arch64 - Yes arm - Yes bfin - ? i38

Re: [gcc] Enable TLS support for RTEMS in libstdc++

On Wed, Jun 8, 2022 at 8:47 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 08/06/2022 15:39, Joel Sherrill wrote: > > Is TLS actually supported on all targets except MIPS? > > I only added MIPS since this target has a fundamental issue with the TLS

Re: [gcc] Enable TLS support for RTEMS in libstdc++

On 08/06/2022 15:39, Joel Sherrill wrote: Is TLS actually supported on all targets except MIPS? I only added MIPS since this target has a fundamental issue with the TLS support. Which target would you also exclude? -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim

Re: [gcc] Enable TLS support for RTEMS in libstdc++

Is TLS actually supported on all targets except MIPS? --joel On Wed, Jun 8, 2022 at 1:51 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > libstdc++-v3/ChangeLog: > > * crossconfig.m4 (*-rtems*): Enable TLS support for all RTEMS > targets >

[gcc] Enable TLS support for RTEMS in libstdc++

libstdc++-v3/ChangeLog: * crossconfig.m4 (*-rtems*): Enable TLS support for all RTEMS targets except mips. --- libstdc++-v3/crossconfig.m4 | 7 +++ 1 file changed, 7 insertions(+) diff --git a/libstdc++-v3/crossconfig.m4 b/libstdc++-v3/crossconfig.m4 index ae5283b7ad3

[PATCH] bsp/mrm332: Fix TLS support in linker command file

--- bsps/m68k/mrm332/start/linkcmds | 16 ++-- spec/build/bsps/m68k/mrm332/tstmrm332.yml | 2 -- 2 files changed, 6 insertions(+), 12 deletions(-) diff --git a/bsps/m68k/mrm332/start/linkcmds b/bsps/m68k/mrm332/start/linkcmds index 7c31b92dd1..3ae0d027bd 100644 --- a/bsps/m

[PATCH 3/6] nios2: Add TLS support

Update #4214. --- .../cpu/nios2/nios2-context-initialize.c | 19 +++ 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/cpukit/score/cpu/nios2/nios2-context-initialize.c b/cpukit/score/cpu/nios2/nios2-context-initialize.c index 1b7d1bbc9e..6950ce4bd6 100644 --- a/

Re: TLS Support

> > At this point, I know mips and x86 are broken. x86 looks like some > moderately straight forward > work. MIPS looks harder. The MIPS TLS support is quite well documented here: https://www.linux-mips.org/wiki/NPTL We just need an exception handler to deal with the "rdhwr"

Re: TLS Support

On 28/01/16 21:17, Gedare Bloom wrote: Do we have a list of target architectures with working TLS? https://docs.rtems.org/doc-current/share/rtems/html/cpu_supplement/index.html Is it worth compiling such a list? Its worth to keep this information up to date. -- Sebastian Huber, embedded b

TLS Support

Do we have a list of target architectures with working TLS? Is it worth compiling such a list? ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel