https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16351
--- Comment #26 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to pmatos from comment #25) > (In reply to Manuel López-Ibáñez from comment #24) > > I can give you many examples of old "must-have" bugs that are "easy" to fix, > > but simply there is no one with enough time and motivation to get them done. > > It would be interesting to have that list. Or just those on the top of your > head. I might not necessarily look at them now but I know I will have some > time in the near future to work on a few of these, so it would be > interesting to have this list so I can look at them. A good place to start is https://gcc.gnu.org/bugzilla/buglist.cgi?keywords=easyhack&list_id=116934&order=bug_id&query_format=advanced In particular, PR19808 should be fairly easy and there is some work already done. It is also a prerequisite for PR2972. PR7652 has an initial patch. PR23087 is very straightforward. PR17896 has a patch already. PR99 is the oldest bug in my list and it is still a mystery. It needs proper debugging to understand what goes wrong. Of course, there are also quite a few very old bugs where the fix is not so straight-forward but the impact would be very high: PR19430 (do the warning in the FE?) and PR18501 (the most common Wuninitialized bug).
