search for: max_opts

...ooper at apple.com> Subject: Re: [llvm-dev] RFC: New support for triaging optimization-related failures in front ends Hi, I'm late to the party on this one due to having been off on my holidays but I wanted to add an enthusiastic +1 to this idea. I presented our SNC compiler's similar max_opts approach at EuroLLVM 2014 (slide 38 onwards in http://llvm.org/devmtg/2014-04/PDFs/Talks/GBedwell_PS4CPUToolchain_EuroLLVM2014_distribution.pdf ) so I'm very excited to see this. In that compiler we had it implemented per-transformation so a single difference between max_opts levels would oft...

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.