This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] TARGET_MEM_REF
On Sat, Mar 05, 2005 at 10:38:11AM +0100, Zdenek Dvorak wrote:
> + @item TARGET_MEM_REF
> + These nodes represent memory accesses whose address directly map to
> + an addressing mode of the target architecture. The first argument
> + is @code{TMR_SYMBOL} and must be a @code{VAR_DECL} of an object with
> + a fixed address. The second argument is @code{TMR_BASE} and the
> + third one is @code{TMR_INDEX}. The fourth argument is
> + @code{TMR_STEP} and must be an @code{INTEGER_CST}. The fifth
> + argument is @code{TMR_OFFSET} and must be an @code{INTEGER_CST}.
> + Any of the arguments may be NULL if the appropriate component
> + does not appear in the address. Address of the @code{TARGET_MEM_REF}
> + is determined in the following way.
> +
> + @smallexample
> + &TMR_SYMBOL + TMR_BASE + TMR_INDEX * TMR_STEP + TMR_OFFSET
> + @end smallexample
Would you like to explain what these names are for? In
particular, why are SYMBOL and BASE different?
While I might could see how such a construct could be
useful, I wonder how it integrates with COMPONENT_REFs
and ARRAY_REFs.
The spec numbers were sort of underwhelming. Is this
because rtl loop optimizers fix things up after the fact?
r~