This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Undefined behavior in genautomata.c?
On Mon, 2005-09-19 at 15:07 +0200, Jakub Jelinek wrote:
> On Mon, Sep 19, 2005 at 09:03:48AM -0400, Daniel Berlin wrote:
> > Anyway, the real fix is to simply not attempt to derive information when
> > the access is through a pointer (IE it is not related to structs at all,
> > it's the fact that these are heap allocated), unless you have info about
> > the malloc sites and the upper bound on what size it is allocating.
> >
> > I'll actually soon be providing you such malloc site size info :)
>
> tree-object-size.c already provides that...
1. Not interprocedurally.
2. Not for regular objects, only things involved with
builtin_object_siz.
Most people don't do interesting things in the same function they
allocate in, at least in object oriented languages.
tree-object-size is also a bit hard to follow, in part because it does
things like:
if (object_size_type & 2)
*all over the place*, and says to go look at the builtin_object_size
documentation. It would have been nice to give the existing bits
symbolic names of some sort :)
>
> Jakub