search for: stripdebuginfo

...rsion. 195494: Debug Info: add a constant for debug info version number. 195495: Debug Info: add a "Debug Info Version" module flag to output the current debug info version number. 195504: Debug Info: update testing cases to specify the debug info version number. 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to DebugInfo.cpp. 195535: Debug Info: update testing cases to specify the debug info version number. 196143: Expand comments for Debug Info Version. 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to Metadata.h. 196145: Debug Info: Move the constant f...

...Xalan_base.clang_O0_g 11079688 Xalan_base.gcc_O0 16437776 Xalan_base.gcc_O0_gmlt 54221056 Xalan_base.gcc_O0_g WDYT of implementing similar option in Clang? Clearly, there are two options: 1. Don't modify Clang codegen, but instead erase all the extra debug info by LLVM (pro - there actually is StripDebugInfo pass already, but it's very short and easy, and would have to be patched a lot). 2. Emit less information in Clang. We're also quite interested if this may reduce the compilation time as well. Which approach looks better in your opinion? I'd like to start working on that enhancement, bu...

...r debug info version number. >> 195495: Debug Info: add a "Debug Info Version" module flag to output the >> current debug info version number. >> 195504: Debug Info: update testing cases to specify the debug info version >> number. >> 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to >> DebugInfo.cpp. >> 195535: Debug Info: update testing cases to specify the debug info version >> number. >> 196143: Expand comments for Debug Info Version. >> 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to >&g...

...o: add a constant for debug info version number. > 195495: Debug Info: add a "Debug Info Version" module flag to output the > current debug info version number. > 195504: Debug Info: update testing cases to specify the debug info version > number. > 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to > DebugInfo.cpp. > 195535: Debug Info: update testing cases to specify the debug info version > number. > 196143: Expand comments for Debug Info Version. > 196144: Debug Info: Move the constant for Debug Info Version from Dwarf.h to > Metadata.h. > 1961...

...number. >>> 195495: Debug Info: add a "Debug Info Version" module flag to output the >>> current debug info version number. >>> 195504: Debug Info: update testing cases to specify the debug info version >>> number. >>> 195505: Debug Info: move StripDebugInfo from StripSymbols.cpp to >>> DebugInfo.cpp. >>> 195535: Debug Info: update testing cases to specify the debug info version >>> number. >>> 196143: Expand comments for Debug Info Version. >>> 196144: Debug Info: Move the constant for Debug Info Version fr...

...79688 Xalan_base.gcc_O0 > 16437776 Xalan_base.gcc_O0_gmlt > 54221056 Xalan_base.gcc_O0_g > > WDYT of implementing similar option in Clang? Clearly, there are two options: > 1. Don't modify Clang codegen, but instead erase all the extra debug info by LLVM (pro - there actually is StripDebugInfo pass already, but it's very short and easy, > and would have to be patched a lot). > 2. Emit less information in Clang. We're also quite interested if this may reduce the compilation time as well. > Which approach looks better in your opinion? I'd like to start working on that...

...loading a module never sees out of date debug info metadata) >> we ensure we only have to change one place, not every client of bitcode >> loading. >> > > We can drop the debug info in the auto upgrading path similar to how we > upgrade TBAA tags. > I am going to move StripDebugInfo from StripSymbols.cpp to DebugInfo.cpp > so the implementation can be shared between StripSymbols and AutoUpgrade. > After that, a sample patch looks like: > Index: include/llvm/AutoUpgrade.h > =================================================================== > --- include/llvm/Aut...

...ble (so that > any LLVM code loading a module never sees out of date debug info metadata) > we ensure we only have to change one place, not every client of bitcode > loading. > We can drop the debug info in the auto upgrading path similar to how we upgrade TBAA tags. I am going to move StripDebugInfo from StripSymbols.cpp to DebugInfo.cpp so the implementation can be shared between StripSymbols and AutoUpgrade. After that, a sample patch looks like: Index: include/llvm/AutoUpgrade.h =================================================================== --- include/llvm/AutoUpgrade.h (revision 195...

...sees out of date debug info metadata) >>> we ensure we only have to change one place, not every client of bitcode >>> loading. >> >> >> We can drop the debug info in the auto upgrading path similar to how we >> upgrade TBAA tags. >> I am going to move StripDebugInfo from StripSymbols.cpp to DebugInfo.cpp >> so the implementation can be shared between StripSymbols and AutoUpgrade. >> After that, a sample patch looks like: >> Index: include/llvm/AutoUpgrade.h >> =================================================================== >>...

...a) > >>> we ensure we only have to change one place, not every client of bitcode > >>> loading. > >> > >> > >> We can drop the debug info in the auto upgrading path similar to how we > >> upgrade TBAA tags. > >> I am going to move StripDebugInfo from StripSymbols.cpp to DebugInfo.cpp > >> so the implementation can be shared between StripSymbols and > AutoUpgrade. > >> After that, a sample patch looks like: > >> Index: include/llvm/AutoUpgrade.h > >> ====================================================...

Hiya, Is there any easy way to remove the debug info from the LLVM byte code once I have collected all the debug info I needed? It is because the debug info seems to slow down the program significantly. I may be able to go through each basic block and delete the debug info in my pass. But, is there any elegant way to do it? Cheers, Zheng

Hi Zheng, > Is there any easy way to remove the debug info from the LLVM byte code > once I have collected all the debug info I needed? It is because the > debug info seems to slow down the program significantly. I may be able > to go through each basic block and delete the debug info in my pass. > But, is there any elegant way to do it? the opt tool has an option called

On Thu, Nov 21, 2013 at 11:45 AM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 11:26 AM, David Blaikie <dblaikie at gmail.com>wrote: > >> >> >> >> On Thu, Nov 21, 2013 at 11:06 AM, Manman Ren <manman.ren at gmail.com>wrote: >> >>> >>> >>> >>> On Thu, Nov 21, 2013 at

...change one place, not every client of >> >>> bitcode >> >>> loading. >> >> >> >> >> >> We can drop the debug info in the auto upgrading path similar to how we >> >> upgrade TBAA tags. >> >> I am going to move StripDebugInfo from StripSymbols.cpp to >> >> DebugInfo.cpp >> >> so the implementation can be shared between StripSymbols and >> >> AutoUpgrade. >> >> After that, a sample patch looks like: >> >> Index: include/llvm/AutoUpgrade.h >> >> =====...

...not modify the DI. But I'm not sure if there's a way to achieve this. I'm not sure if there's a way to do this, but I see it as an optimization that can be deferred for now. > I'm currently trying to strip debug info after each CheckDebugify. There's a function called StripDebugInfo which does this. vedant > I have been searching everywhere but can't seem to find an API to remove MDNodes. I have seen a MDNode::deleteAsSubclass() method, unfortunately it is private.I guess nobody has ever needed to remove MDNodes/Metadata before. Can you give me some advice on how to...

...re's a way to achieve > this. > > > I'm not sure if there's a way to do this, but I see it as an optimization > that can be deferred for now. > > > I'm currently trying to strip debug info after each CheckDebugify. > > > There's a function called StripDebugInfo which does this. > Wow thanks, I was reimplementing that function.... > > vedant > > > I have been searching everywhere but can't seem to find an API to remove > MDNodes. I have seen a *MDNode::deleteAsSubclass() *method, unfortunately > it is private.I guess nobody ha...

Hi Vedant, I have tried to implement the fix you proposed, but it didn't work as expected. I created a new *Module* Pass Manager (not Function Pass Manager) and override the *add()* method like this: class DebugifyEachPassManager : public legacy::PassManager { public: void add(Pass *P) override { PassManager::add(createDebugifyPass()); PassManager::add(P);

Mhm I see now, thanks for your explanation! Son Tuan Vu On Fri, Mar 16, 2018 at 10:58 PM, Vedant Kumar <vsk at apple.com> wrote: > > On Mar 16, 2018, at 2:30 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > Hi Vedant, > > Thank you for your reply. I think I can make this debugify-each mode, but > I guess this is reserved for your GSoC project ? > >