search for: approximateloopsize

Hi, just a quick question about the intent of the ApproximateLoopSize() function in LoopUnroll.cpp: If a loop contains debug stoppoint intrinsics, does it make sense to count them? My understanding is that they are removed when not running under llvm-db anyway, so we probably shouldn't make size judgements based on them. Is that right, or am I missing something?...

...ze of some code to determine whether to unroll it or >> > not. This means that it should be enhanced to ignore debug >> > intrinsics for the sake of code size estimation. >> > > The loop unrolling pass already ignores the debug info! See > LoopUnroll.cpp::ApproximateLoopSize() > ok, I see. > >> > >> > Another example is optimizations like SimplifyCFG when it merges if/ >> > then/else into select instructions. SimplifyCFG will have to be >> > enhanced to ignore debug intrinsics when doing its safety/ >> > prof...

Hi, I've been thinking about how to keep the line number with the llvm transform/Analysis passes. Basically, I agree with Chris's notes ( http://www.nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt), and I will follow his way to turn on the line number information when optimization enabled. Here is a detailed proposal: 1. Introduction At the time of this writing, LLVM's