Re: New TLS usage in libgcc_s.so.1, compatibility impact

[Florian Weimer <fweimer@redhat.com>]

* Iain Sandoe:

>> On 15 Jan 2024, at 15:35, Florian Weimer <fweimer@redhat.com> wrote:
>> 
>> * Carlos O'Donell:
>> 
>>> I agree. TLS should be seen more like .bss/.data rather than something
>>> that is allocated with malloc().
>> 
>> There wasn't consensus regarding this in 2014.  See below.
>> 
>>> If we leak memory via TLS that is a glibc bug that we can deal with,
>> 
>> This is something that libgcc_s.so.1 does in GCC 14 if the heap
>> trampolines are used.
>
> Is there a GCC BZ for this?
> (if there is something we should address in GCC, it would be better sooner)

Sorry, I wanted to write a reproducer first.  With it, I found two more
issue.

  Memory (resource) leak in -ftrampoline-impl=heap
  <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401>

  Incorrect symbol versions for __builtin_nested_func_ptr_created,
  __builtin_nested_func_ptr in libgcc_s.so.1
  <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113402>

  __builtin_nested_func_ptr_created, __builtin_nested_func_ptr should be
  dynamically linked by default
  <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113403>

Thanks,
Florian