search for: direfmap

...at >> would help reduce debug info metadata further if that's >> useful/necessary. > > Exactly. While the above patch will cover up the problem, we will still have many duplicate type entries during LTO that will take up memory, even though only the last one to be entered into DIRefMap will actually be used for emitting DWARF. Since DIRefs are also more expensive in terms of lookup speed, I think I’d prefer to only use them only where necessary (=as far down the MDNode DAG as possible). > Right, though, to be fair, some numbers here might be nice. The tradeoff of "extra...

...duce debug info metadata further if that's >>>> useful/necessary. >>> >>> Exactly. While the above patch will cover up the problem, we will still have many duplicate type entries during LTO that will take up memory, even though only the last one to be entered into DIRefMap will actually be used for emitting DWARF. Since DIRefs are also more expensive in terms of lookup speed, I think I’d prefer to only use them only where necessary (=as far down the MDNode DAG as possible). >>> >> >> Right, though, to be fair, some numbers here might be nice. T...

...further if that's >>>>>> useful/necessary. >>>>> >>>>> Exactly. While the above patch will cover up the problem, we will still have many duplicate type entries during LTO that will take up memory, even though only the last one to be entered into DIRefMap will actually be used for emitting DWARF. Since DIRefs are also more expensive in terms of lookup speed, I think I’d prefer to only use them only where necessary (=as far down the MDNode DAG as possible). >>>>> >>>> >>>> Right, though, to be fair, some numbe...

...>>>>>>>> useful/necessary. >>>>>>> >>>>>>> Exactly. While the above patch will cover up the problem, we will still have many duplicate type entries during LTO that will take up memory, even though only the last one to be entered into DIRefMap will actually be used for emitting DWARF. Since DIRefs are also more expensive in terms of lookup speed, I think I’d prefer to only use them only where necessary (=as far down the MDNode DAG as possible). >>>>>>> >>>>>> >>>>>> Right, though,...

On Tue, Jun 24, 2014 at 2:38 PM, Adrian Prantl <aprantl at apple.com> wrote: > I will take this. > > !5 = metadata !{metadata !"./test.h", metadata !"/Volumes/Data/radar/17052973"} > !6 = metadata !{i32 786489, metadata !5, null, metadata !"test", i32 1} ; [ DW_TAG_namespace ] [test] [line 1] > !4 = metadata !{i32 786434, metadata !5, metadata !6,