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! ;) cheers, DaveK -- Can't think of a witty .sigline today....