On Wed, May 14, 2025 at 9:26 AM Richard Biener
wrote:
>
> On Wed, May 14, 2025 at 5:25 AM Kyle Huey wrote:
> >
> > For a debugger to display statically-allocated[0] TLS variables the compiler
> > must communicate information[1] that can be used in conjunction with
ata to be ignored by the linker.
[4] ate_kind_rtx_dtprel exists, after all, and new_addr_loc_descr does produce
it where appropriate.
[5] e.g. an address in the .tbss/.tdata section.
[6] e.g. on x86-64 by examining %fsbase and the offset in the assembly
2025-05-01 Kyle Huey
*
On Mon, May 5, 2025 at 6:45 AM Richard Biener
wrote:
>
> On Mon, May 5, 2025 at 3:37 PM Kyle Huey wrote:
> >
> > On Thu, May 1, 2025 at 11:22 PM Richard Biener
> > wrote:
> > >
> > > On Fri, May 2, 2025 at 2:14 AM Kyle Huey wrote:
> > > >
On Thu, May 1, 2025 at 11:22 PM Richard Biener
wrote:
>
> On Fri, May 2, 2025 at 2:14 AM Kyle Huey wrote:
> >
> > For a debugger to display statically-allocated[0] TLS variables the compiler
> > must communicate information[1] that can be used in conjunction with
ata to be ignored by the linker.
[4] ate_kind_rtx_dtprel exists, after all, and new_addr_loc_descr does produce
it where appropriate.
[5] e.g. an address in the .tbss/.tdata section.
[6] e.g. on x86-64 by examining %fsbase and the offset in the assembly
2025-05-01 Kyle Huey
*
