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:
> > > >
> > > > For a debugger to display statically-allocated[0
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:
> > >
> > > For a debugger to display statically-allocated[0] TLS variables the
> > > compiler
> > > must communicate information[1
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
> > knowledge
> > of the runtime
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 knowledge
> of the runtime enviroment[2] to calculate a location for the variable for
> each threa
For a debugger to display statically-allocated[0] TLS variables the compiler
must communicate information[1] that can be used in conjunction with knowledge
of the runtime enviroment[2] to calculate a location for the variable for
each thread. That need gives rise to dw_loc_dtprel in dwarf2out, a fl
