This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Design issues with multiple IRs
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 6 Dec 2001 20:48:02 +0000
- Subject: Re: [RFC] Design issues with multiple IRs
- References: <20011206143203.B8021@tornado.cygnus.com>
Diego Novillo wrote:-
> Another place where we are abusing void pointers is in
> annotations attached to flowgraph nodes and trees. The 'aux'
> fields are being used to hold analysis information. For
> instance, trees use the 'aux' pointer to hold a pointer to the
> basic block that contains the tree (only for statement trees), a
> pointer to a list of references for VAR_DECLs, a pointer to the
> most recent definition of a VAR_DECL (for building the SSA web).
Why not use a union?
If you give it a single letter, access is not so tedious, or wrap it
in a macro like we do now. But if you can make even a bit of progress
on getting away from "everything is a tree" to "everything is a
pointer to a specific type" like we discussed the other day, that
would be great.
Neil.