search for: autochop

...will get us maybe 70% of the functionality in one easy step, then individual passes can be instrumented as anyone has time or need to get us the rest of the way there. Your max_opt option sounds just like what I’m hoping to achieve here. Personally, I’d love to see some open source version of the autochop system. The more pieces of this we can get into trunk, the less everyone has to keep re-inventing solutions to this shared problem. I think there is a lot of opportunity here for growing this functionality through connecting scripts and other tools. -Andy From: Greg Bedwell [mailto:gregbedwell...

I agree that the more fine grained this becomes the more useful it can be. I’ve updated my prototype to use a single number approach. I’m going to clean this up and post a review in the next day or two. -Andy From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Pete Cooper via llvm-dev Sent: Friday, March 25, 2016 10:22 PM To: Matthias Braun <matze at braunis.de> Cc:

I've worked on a compiler with a counter, but for individual optimisations, not just passes. It was incredibly useful! In the llvm world, it would let you bisect exactly which instcombine, dagcombine, or whatever causes an issue. I support the addition of a pass counter if it helps bisecting, but just wanted to point out that this can be as fine grained as the community is willing to accept.