"H.J. Lu" wrote:
> OPTION_GLIBC can't be used here since OPTION_GLIBC is
> evaluated at run-time:
>
> https://gcc.gnu.org/pipermail/gcc-regression/2022-January/076271.html
Oops, my bad, sorry! This accidentally broke in one of the two cleanup
commits. Originally I justed use TARGET_GLIBC_MAJOR
On Sat, Dec 18, 2021 at 4:20 AM soeren--- via Gcc-patches
wrote:
>
> From: Sören Tempel
>
> The -fsplit-stack option requires the pthread_t TCB definition in the
> libc to provide certain struct fields at specific hardcoded offsets. As
> far as I know, only glibc provides these fields at the
On Thu, Jan 20, 2022 at 11:52 PM Richard Sandiford
wrote:
>
> cc:ing the x86 and s390 maintainers
>
> soeren--- via Gcc-patches writes:
> > From: Sören Tempel
> >
> > The -fsplit-stack option requires the pthread_t TCB definition in the
> > libc to provide certain struct fields at specific
On 1/20/22 23:52, Richard Sandiford wrote:
> cc:ing the x86 and s390 maintainers
>
> soeren--- via Gcc-patches writes:
>> From: Sören Tempel
>>
>> The -fsplit-stack option requires the pthread_t TCB definition in the
>> libc to provide certain struct fields at specific hardcoded offsets. As
>>
cc:ing the x86 and s390 maintainers
soeren--- via Gcc-patches writes:
> From: Sören Tempel
>
> The -fsplit-stack option requires the pthread_t TCB definition in the
> libc to provide certain struct fields at specific hardcoded offsets. As
> far as I know, only glibc provides these fields at the
Ping.
Summary: Patch disable -fstack-split on non-glibc targets to prevent
corruptions of the TCB on libcs which do not support the required
fields in pthread_t. This is an important fix for having gccgo work on
musl by default.
See:
From: Sören Tempel
The -fsplit-stack option requires the pthread_t TCB definition in the
libc to provide certain struct fields at specific hardcoded offsets. As
far as I know, only glibc provides these fields at the required offsets.
Most notably, musl libc does not have these fields. However,
