http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59520
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-12-20
Ever confirmed|0 |1
Severity|normal |minor
--- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Zhendong Su from comment #4)
> It would be nice to see that this gets fixed eventually [...]
> it would be great to see this aspect of compilers
> also gets better to become more "friendly" to beginners (and professionals
> too).
I think everybody working on GCC would agree with you. But the number of people
working on GCC is very limited and they have a finite amount of time to
dedicate to it. So either you convince new people to start working on GCC or
yourself start contributing. Fixing this bug for example may be easy or may
require some effort, but given that it surely affects very few people using
non-standard code and there are also easy work-arounds, people already working
on GCC will likely spent their time on something else.
If you consider this issue important, just set-up a build environment, launch
gdb and start hacking. You can grep for the error message, set a breakpoint at
the error line and analyze why it is emitted and how you can modify the code to
follow the warning route. If you get it fixed before the end of January, it
will be in GCC 4.9.
Be the change you wish to see!
