This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [PATCH] Re: ref_contains_indirect_ref always false?
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: 'Diego Novillo' <dnovillo at redhat dot com>, 'Richard Kenner' <kenner at vlsi1 dot ultra dot nyu dot edu>, 'Richard Guenther' <rguenther at suse dot de>, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 04 Nov 2005 11:27:21 -0500
- Subject: RE: [PATCH] Re: ref_contains_indirect_ref always false?
- References: <SERRANOYSl1q4gtopWd00000180@SERRANO.CAM.ARTIMI.COM>
On Fri, 2005-11-04 at 16:23 +0000, Dave Korn wrote:
> Daniel Berlin wrote:
>
> > The use in tree-ssa-loop-niter.c is really trying to skip out on
> > inferring loop bounds from pointer to structure accesses in the case of
> > things like:
> >
> >
> > struct a
> > {
> > char foo[1];
> > };
> >
> >
> > struct a *b = malloc (sizeof (struct a) + 100);
> > b->foo = "I like candy!"
> >
> >
> > Since we have to keep this working:)
>
>
> We do?! Storing a pointer value to a char variable has never worked very
> well so far!
I was shorthanding it, you know what i meant :)