search for: d46100

...39;s difficult to split up work on this, consider working on enhancing opt's -verify-each mode so that it runs after each pass in -O1/-O2/etc. This would help address use-before-def scenarios with debug info intrinsics. There's an ongoing discussion about this here: https://reviews.llvm.org/D46100 <https://reviews.llvm.org/D46100>. > But what about Call Graph SCC Pass and Loop Pass? Great question! It might not be worthwhile to shoehorn what debugify does onto cgscc passes. The major cgscc pass I know of is the inliner, and its handling of debug info can be tested in a more targe...

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);

> On May 7, 2018, at 11:29 PM, Jonas Paulsson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, (Resent with proper subject line) > > I recently found myself in trouble because the crash I had disappeared > with -g, so I could not debug the program. This happened because the > optimizer did not remember to consider DBG_VALUEs

Hi, (Resent with proper subject line) I recently found myself in trouble because the crash I had disappeared with -g, so I could not debug the program. This happened because the optimizer did not remember to consider DBG_VALUEs instruction so it changed its behavior, and the bug went hiding. I then started discussing this onhttps://reviews.llvm.org/D45878, and

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 ? > >

...lit up work on this, consider working > on enhancing opt's -verify-each mode so that it runs after each pass in > -O1/-O2/etc. This would help address use-before-def scenarios with debug > info intrinsics. There's an ongoing discussion about this here: > https://reviews.llvm.org/D46100. > > Yes I am still waiting for Chandler's thoughts on verify-each mode of LegacyPassManager (because it works if we use the new PassManager) and on what would be the best way to tackle it. > But what about *Call Graph SCC Pass* and *Loop Pass*? > > > Great question! It might...