>
> On Mon, Jun 23, 2014 at 06:43:20PM +0100, Jan Hubicka wrote:
> > > On Mon, 23 Jun 2014, James Greenhalgh wrote:
> > >
> > > >
> > > > Hi,
> > > >
> > > > pr61510 is a case where cgraphunit.c::analyze_functions can end up
> > > > dereferencing a NULL pointer. This is, to me, the obvious way to
On Mon, Jun 23, 2014 at 06:43:20PM +0100, Jan Hubicka wrote:
> > On Mon, 23 Jun 2014, James Greenhalgh wrote:
> >
> > >
> > > Hi,
> > >
> > > pr61510 is a case where cgraphunit.c::analyze_functions can end up
> > > dereferencing a NULL pointer. This is, to me, the obvious way to avoid
> > > derefe
On Mon, Jun 23, 2014 at 06:43:20PM +0100, Jan Hubicka wrote:
> > On Mon, 23 Jun 2014, James Greenhalgh wrote:
> >
> > >
> > > Hi,
> > >
> > > pr61510 is a case where cgraphunit.c::analyze_functions can end up
> > > dereferencing a NULL pointer. This is, to me, the obvious way to avoid
> > > dere
> On Mon, 23 Jun 2014, James Greenhalgh wrote:
>
> >
> > Hi,
> >
> > pr61510 is a case where cgraphunit.c::analyze_functions can end up
> > dereferencing a NULL pointer. This is, to me, the obvious way to avoid
> > dereferencing NULL.
> >
> > However, I'm not very confident that this isn't just
On Mon, 23 Jun 2014, James Greenhalgh wrote:
>
> Hi,
>
> pr61510 is a case where cgraphunit.c::analyze_functions can end up
> dereferencing a NULL pointer. This is, to me, the obvious way to avoid
> dereferencing NULL.
>
> However, I'm not very confident that this isn't just masking some
> horr