https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94997
--- Comment #5 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Martin Sebor from comment #4) > ... I see more overhead than value in reports suggesting > these types of improvements to the code base. Righto. I've provided the list of all known 237 places, so I won't report any more from the list. I've checked about 20 of them and they look valid to me, but there could be some false positives. > If you think they're worthwhile to make, just do it. > You can submit a patch for review but you > don't even need to ask for approval to commit it (see > https://www.gnu.org/software/gcc/svnwrite.html#all). Thanks but no. I prefer to encourage other developers to write into gcc repository than do it myself. > OTOH, where I see much more value is in adding features to detect these > opportunities and adding them to -Wall (and for those, having reports in > Bugzilla is also important). Agreed. I find the best first step to getting a new feature into gcc is to point out as many as possible places in the source code of gcc where that feature would help. Whether 237 cases is enough is now in the hands of a keen developer with enough time to implement the feature.
