This is the mail archive of the
mailing list for the GCC project.
Re: New problem compiling g-exctra.adb
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: dnovillo at redhat dot com, gcc at gcc dot gnu dot org
- Date: Tue, 07 Sep 2004 21:49:48 -0400
- Subject: Re: New problem compiling g-exctra.adb
- References: <10409080126.AA29420@vlsi1.ultra.nyu.edu>
On Tue, 2004-09-07 at 21:26 -0400, Richard Kenner wrote:
> I'm not well versed in standards and such, but if that's the case, you
> want to create a name tag for such a pointer.
> To solicit name tag creation, you have to tell create_name_tags() about
> the pointer. Currently it creates name tags for pointers with PT_VARS
> and pointers with PT_MALLOC.
> One approach is to set the PT_MALLOC attribute on these pointers with
> value 0. If you do that, things should just work. The name would
> probably need to be changed, but PT_MALLOC has the semantics you are
> looking for. It means 'points to a chunk of memory that cannot be used
> by a regular user variable'.
> Why can't we just ignore assignments of pointers to zero? They would
> seem to tell us nothing useful about the variable being assigned.
> What am I missing?
Actually, this is probably exactly what you should do.
Unless you want to know what may point to null for some reason.