This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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
    tree nodes.

    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.
See http://gcc.gnu.org/ml/gcc/2004-06/msg01376.html.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]