Hi, On Mon, Jul 18, 2016 at 11:28:48AM -0400, NightStrike wrote: > Well, one thing to note is that the warning is an easy way to get a > notice of a possible missed optimization (and I have many more > occurrences of it in a particular code base that I use). If the > warning is highlighted potential issues that aren't due to the -f > option but are issues nonetheless, and we remove the warning, then how > should I go about finding these missed opportunities in the future? > Is there a different mechanism that does the same thing?
Yes, -fopt-info and -fopt-info-OPTIONS switches. It certainly seems to be a more natural means for manual compiler-guided optimization than warnings. Martin
