This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH]: MEM_REF
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: rakdver at atrey dot karlin dot mff dot cuni dot cz
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Mon, 16 May 05 21:17:11 EDT
- Subject: Re: [PATCH]: MEM_REF
I assume you allow representing things like p[i].x as COMPONENT_REF
(MEM_REF (p, i), x)? If so, I would somewhat prefer having MEM_REF
(ugh .. perhaps with a different name) and TARGET_MEM_REF as separate
The purposes of the nodes are really quite different, and
TARGET_MEM_REFs as implemented now satisfy some invariants useful
mostly in the very late tree optimizations. In particular
TARGET_MEM_REF is never nested with other memory reference nodes (like
COMPONENT_REFs or ARRAY_REFs) -- it just represents the flat access to
memory, mapping directly to MEM node on rtl.
I made a proposal quite a while ago for yet another way to do this.