Hello, On Wed, 22 Apr 2020, Erick Ochoa wrote:
> in order for me to debug my issue, I'm going to have to refactor passes > which directly reference optimize. For debugging you can also work backwards: use -O3 and add -fno-xy options. At least you then know (after disabling all O3 passes) that it's one of those places that explicitely are tacked off the opt level. > I am planning on refactoring them by creating a "$pass_opt_level". This > variable can be set via command line or somewhere in opts.c. I can then > substitute the references to optimize with $pass_opt_level. I think for local decisions in passes that currenly use 'optimize' the better strategy is to determine the underlying cause for having that test, and add a flag for that (or reuse an existing one, e.g. if the reason was "don't disturb debugging experience" then create or use a flag specific to that role). For the global decisions mentioned by Jakub: that's by nature not specific to a pass, hence a per-pass opt level wouldn't help. Ciao, Michael.
