On 10/15/14 00:55, Richard Biener wrote:
On Tue, Oct 14, 2014 at 10:07 PM, Aldy Hernandez <al...@redhat.com> wrote:
On 10/14/14 06:21, Richard Biener wrote:
On Tue, Oct 14, 2014 at 2:48 AM, Aldy Hernandez <al...@redhat.com> wrote:
Another similar issue I've seen is handling DW_TAG_lexical_block
(gen_lexical_block_die). Ideally we should generate the
DW_TAG_lexical_block and the corresponding locals in early dumping, and then
fill in the high/low attributes of the lexical block the second time around.
We would need a hash similar to decl_die_table to get from
BLOCK->DW_TAG_lexical_block, similar to die_table_offset. For that matter,
we could store the relationship in die_table_offset, or in the die_offset if
I understood things correctly.
Yes, we'd create the DW_TAG_lexical_block early, store and stream a
reference to the early DIE in the BLOCK and annotate that DIE
late by means of some clever dwarf tricks.
I didn't realize adding fields/bits to the tree structure was on the
table. This makes things simpler.
That being said, it seems like a lot of this will become clearer as I
implement it. Thanks so much for the guidance. I'll now go off into a
little dark corner and think about this some more while I crank out some
incremental patches.
Thanks again.
Aldy
