search for: seenmodulevaluesrecord

...s. It should pick up lots of other stuff, depending on > > how much inlining has happened. > > > > (I have a draft of the writer side, still working on the reader.) > > Teresa: I had trouble make this work with the delayed metadata parsing > (the logic around "SeenModuleValuesRecord"). My WIP patch rips that > out rather unceremoniously. > > (Attached the patch for reference, but it needs to be cleaned up, split > up, etc.; not ready for review (although comments always welcome)). > > My understanding from Mehdi is that maybe ThinLTO isn't currently...

...rgeting > `DILocation`s. It should pick up lots of other stuff, depending on > how much inlining has happened. > > (I have a draft of the writer side, still working on the reader.) Teresa: I had trouble make this work with the delayed metadata parsing (the logic around "SeenModuleValuesRecord"). My WIP patch rips that out rather unceremoniously. (Attached the patch for reference, but it needs to be cleaned up, split up, etc.; not ready for review (although comments always welcome)). My understanding from Mehdi is that maybe ThinLTO isn't currently relying on the delayed pars...

...ts of other stuff, depending on >> > how much inlining has happened. >> > >> > (I have a draft of the writer side, still working on the reader.) >> >> Teresa: I had trouble make this work with the delayed metadata parsing >> (the logic around "SeenModuleValuesRecord"). My WIP patch rips that >> out rather unceremoniously. >> >> (Attached the patch for reference, but it needs to be cleaned up, split >> up, etc.; not ready for review (although comments always welcome)). >> >> My understanding from Mehdi is that maybe Thi...

...s of other stuff, depending on >> > how much inlining has happened. >> > >> > (I have a draft of the writer side, still working on the reader.) >> >> Teresa: I had trouble make this work with the delayed metadata parsing >> (the logic around "SeenModuleValuesRecord"). My WIP patch rips that >> out rather unceremoniously. >> >> (Attached the patch for reference, but it needs to be cleaned up, split >> up, etc.; not ready for review (although comments always welcome)). >> >> My understanding from Mehdi is that maybe T...

...s of other stuff, depending on >> > how much inlining has happened. >> > >> > (I have a draft of the writer side, still working on the reader.) >> >> Teresa: I had trouble make this work with the delayed metadata parsing >> (the logic around "SeenModuleValuesRecord"). My WIP patch rips that >> out rather unceremoniously. >> >> (Attached the patch for reference, but it needs to be cleaned up, split >> up, etc.; not ready for review (although comments always welcome)). >> >> My understanding from Mehdi is that maybe T...

...n > >> > how much inlining has happened. > >> > > >> > (I have a draft of the writer side, still working on the reader.) > >> > >> Teresa: I had trouble make this work with the delayed metadata parsing > >> (the logic around "SeenModuleValuesRecord"). My WIP patch rips that > >> out rather unceremoniously. > >> > >> (Attached the patch for reference, but it needs to be cleaned up, split > >> up, etc.; not ready for review (although comments always welcome)). > >> > >> My understandin...

I have some ideas to allow the BitcodeReader to lazy-load debug info metadata, and wanted to air this on llvm-dev before getting too deep into the code. Motivation ========== Based on some analysis Mehdi ran (ping him for details), there are three (related) compile-time bottlenecks we're seeing with `-flto=thin -g`: a) Reading the large number of Metadata bitcode records in the global