On Wed, Jun 01, 2016 at 02:44:22PM +0200, Marcin Baczyński wrote:
> On 1 Jun 2016 14:07, "Jakub Jelinek" <ja...@redhat.com> wrote:
> >
> > On Wed, Jun 01, 2016 at 01:55:04PM +0200, Marcin Baczyński wrote:
> > > PR c/48116.
> > >
> > > Botstrapped and tested on x86_64-pc-linux-gnu.
> > >
> > > gcc/ChangeLog:
> > >
> > > * c/c-typeck.c (c_finish_return): emit warning about return with a
> > > void expression in a function returning void if warn_return_type.
> >
> > This is a GNU extension, so I fail to see why you should warn.
>
> The bug is on the easyhacks list, I thought it would be a good place to
> start digging into the GCC code base.
First of all, I'm not the C FE maintainer, so these are just IMHO comments,
the maintainers might have different opinion.
> Do you have any suggestions for better things to start with?
Welcome to GCC hacking! I'm must say I don't know in what state the easy
hacks list is, but for bugs that have been sitting in bugzilla for many
years there often is a reason why they haven't been addressed - it could be
just lack of interest from anybody, or that they fell through without
anybody noticing, but could be also that they aren't all that easy.
Often the easiest to fix bugs could be among the most recently filed PRs.
Jakub
