On Thu, Sep 27, 2018 at 3:28 AM, Richard Biener wrote:
> On Wed, 26 Sep 2018, Jason Merrill wrote:
>
>> On Wed, Sep 26, 2018 at 9:35 AM, Richard Biener wrote:
>> >
>> > We do not create a DW_AT_lexical_block for the outermost block in
>> > functions but we do for DW_AT_inlined_subroutines. That
On Wed, 26 Sep 2018, Jason Merrill wrote:
> On Wed, Sep 26, 2018 at 9:35 AM, Richard Biener wrote:
> >
> > We do not create a DW_AT_lexical_block for the outermost block in
> > functions but we do for DW_AT_inlined_subroutines. That makes
> > debuginfo look like if there were two of each local,
On Wed, Sep 26, 2018 at 9:35 AM, Richard Biener wrote:
>
> We do not create a DW_AT_lexical_block for the outermost block in
> functions but we do for DW_AT_inlined_subroutines. That makes
> debuginfo look like if there were two of each local, the outer
> one (from the abstract instance) optimize
We do not create a DW_AT_lexical_block for the outermost block in
functions but we do for DW_AT_inlined_subroutines. That makes
debuginfo look like if there were two of each local, the outer
one (from the abstract instance) optimized out (visible via
info locals in gdb).
The following elides th
