* Fāng-ruì Sòng:
>> I *think* you can get what you need via existing GLIBC_PRIVATE
>> interfaces. But in order to describe how to caox the data out of glibc,
>> I need to know what you need.
>
> Unfortunate no, not reliably. Currently _dl_get_tls_static_info
> (https://github.com/llvm/llvm-projec
On Mon, Nov 29, 2021 at 11:30 AM Florian Weimer wrote:
>
> * Fāng-ruì Sòng:
>
> > PING^3
>
> I think the core issue with this patch is like this:
>
> * I do not want to commit glibc to a public API that disallows future
> changes to the way we allocate static TLS. While static TLS objects
> c
* Fāng-ruì Sòng:
> PING^3
I think the core issue with this patch is like this:
* I do not want to commit glibc to a public API that disallows future
changes to the way we allocate static TLS. While static TLS objects
cannot move in memory, the extent of the static TLS area (minimum and
ma
On Tue, Oct 19, 2021 at 12:37 PM Fāng-ruì Sòng wrote:
>
> On Thu, Oct 14, 2021 at 5:13 PM Fangrui Song wrote:
> >
> > On 2021-10-06, Fangrui Song wrote:
> > >On 2021-09-27, Fangrui Song wrote:
> > >>On 2021-09-27, Florian Weimer wrote:
> > >>>* Fangrui Song:
> > >>>
> > Sanitizer runtimes nee
On Thu, Oct 14, 2021 at 5:13 PM Fangrui Song wrote:
>
> On 2021-10-06, Fangrui Song wrote:
> >On 2021-09-27, Fangrui Song wrote:
> >>On 2021-09-27, Florian Weimer wrote:
> >>>* Fangrui Song:
> >>>
> Sanitizer runtimes need static TLS boundaries for a variety of use cases.
>
> * asan/h
