— Macro: HAVE_PRE_INCREMENT
— Macro: HAVE_PRE_DECREMENT
— Macro: HAVE_POST_INCREMENT
— Macro: HAVE_POST_DECREMENT

A C expression that is nonzero if the machine supports pre-increment, pre-decrement, post-increment, or post-decrement addressing respectively.

— Macro: HAVE_PRE_MODIFY_DISP
— Macro: HAVE_POST_MODIFY_DISP

A C expression that is nonzero if the machine supports pre- or post-address side-effect generation involving constants other than the size of the memory operand.

— Macro: HAVE_PRE_MODIFY_REG
— Macro: HAVE_POST_MODIFY_REG

A C expression that is nonzero if the machine supports pre- or post-address side-effect generation involving a register displacement.

— Macro: CONSTANT_ADDRESS_P (x)

A C expression that is 1 if the RTX x is a constant which is a valid address. On most machines the default definition of (CONSTANT_P (x) && GET_CODE (x) != CONST_DOUBLE) is acceptable, but a few machines are more restrictive as to which constant addresses are supported.

— Macro: CONSTANT_P (x)

CONSTANT_P, which is defined by target-independent code, accepts integer-values expressions whose values are not explicitly known, such as symbol_ref, label_ref, and high expressions and const arithmetic expressions, in addition to const_int and const_double expressions.

— Macro: MAX_REGS_PER_ADDRESS

A number, the maximum number of registers that can appear in a valid memory address. Note that it is up to you to specify a value equal to the maximum number that TARGET_LEGITIMATE_ADDRESS_P would ever accept.

— Target Hook: bool TARGET_LEGITIMATE_ADDRESS_P (enum machine_mode mode, rtx x, bool strict)

A function that returns whether x (an RTX) is a legitimate memory address on the target machine for a memory operand of mode mode.

Legitimate addresses are defined in two variants: a strict variant and a non-strict one. The strict parameter chooses which variant is desired by the caller.

The strict variant is used in the reload pass. It must be defined so that any pseudo-register that has not been allocated a hard register is considered a memory reference. This is because in contexts where some kind of register is required, a pseudo-register with no hard register must be rejected. For non-hard registers, the strict variant should look up the reg_renumber array; it should then proceed using the hard register number in the array, or treat the pseudo as a memory reference if the array holds -1.

The non-strict variant is used in other passes. It must be defined to accept all pseudo-registers in every context where some kind of register is required.

Normally, constant addresses which are the sum of a symbol_ref and an integer are stored inside a const RTX to mark them as constant. Therefore, there is no need to recognize such sums specifically as legitimate addresses. Normally you would simply recognize any const as legitimate.

Usually PRINT_OPERAND_ADDRESS is not prepared to handle constant sums that are not marked with const. It assumes that a naked plus indicates indexing. If so, then you must reject such naked constant sums as illegitimate addresses, so that none of them will be given to PRINT_OPERAND_ADDRESS.

On some machines, whether a symbolic address is legitimate depends on the section that the address refers to. On these machines, define the target hook TARGET_ENCODE_SECTION_INFO to store the information into the symbol_ref, and then check for it here. When you see a const, you will have to look inside it to find the symbol_ref in order to determine the section. See Assembler Format.

Some ports are still using a deprecated legacy substitute for this hook, the GO_IF_LEGITIMATE_ADDRESS macro. This macro has this syntax:

          #define GO_IF_LEGITIMATE_ADDRESS (mode, x, label)
     

and should goto label if the address x is a valid address on the target machine for a memory operand of mode mode. Whether the strict or non-strict variants are desired is defined by the REG_OK_STRICT macro introduced earlier in this section. Using the hook is usually simpler because it limits the number of files that are recompiled when changes are made.

— Macro: TARGET_MEM_CONSTRAINT

A single character to be used instead of the default 'm' character for general memory addresses. This defines the constraint letter which matches the memory addresses accepted by TARGET_LEGITIMATE_ADDRESS_P. Define this macro if you want to support new address formats in your back end without changing the semantics of the 'm' constraint. This is necessary in order to preserve functionality of inline assembly constructs using the 'm' constraint.

— Macro: FIND_BASE_TERM (x)

A C expression to determine the base term of address x, or to provide a simplified version of x from which alias.c can easily find the base term. This macro is used in only two places: find_base_value and find_base_term in alias.c.

It is always safe for this macro to not be defined. It exists so that alias analysis can understand machine-dependent addresses.

The typical use of this macro is to handle addresses containing a label_ref or symbol_ref within an UNSPEC.

— Target Hook: rtx TARGET_LEGITIMIZE_ADDRESS (rtx x, rtx oldx, enum machine_mode mode)

This hook is given an invalid memory address x for an operand of mode mode and should try to return a valid memory address.

x will always be the result of a call to break_out_memory_refs, and oldx will be the operand that was given to that function to produce x.

The code of the hook should not alter the substructure of x. If it transforms x into a more legitimate form, it should return the new x.

It is not necessary for this hook to come up with a legitimate address. The compiler has standard ways of doing so in all cases. In fact, it is safe to omit this hook or make it return x if it cannot find a valid way to legitimize the address. But often a machine-dependent strategy can generate better code.

— Macro: LEGITIMIZE_RELOAD_ADDRESS (x, mode, opnum, type, ind_levels, win)

A C compound statement that attempts to replace x, which is an address that needs reloading, with a valid memory address for an operand of mode mode. win will be a C statement label elsewhere in the code. It is not necessary to define this macro, but it might be useful for performance reasons.

For example, on the i386, it is sometimes possible to use a single reload register instead of two by reloading a sum of two pseudo registers into a register. On the other hand, for number of RISC processors offsets are limited so that often an intermediate address needs to be generated in order to address a stack slot. By defining LEGITIMIZE_RELOAD_ADDRESS appropriately, the intermediate addresses generated for adjacent some stack slots can be made identical, and thus be shared.

Note: This macro should be used with caution. It is necessary to know something of how reload works in order to effectively use this, and it is quite easy to produce macros that build in too much knowledge of reload internals.

Note: This macro must be able to reload an address created by a previous invocation of this macro. If it fails to handle such addresses then the compiler may generate incorrect code or abort.

The macro definition should use push_reload to indicate parts that need reloading; opnum, type and ind_levels are usually suitable to be passed unaltered to push_reload.

The code generated by this macro must not alter the substructure of x. If it transforms x into a more legitimate form, it should assign x (which will always be a C variable) a new value. This also applies to parts that you change indirectly by calling push_reload.

The macro definition may use strict_memory_address_p to test if the address has become legitimate.

If you want to change only a part of x, one standard way of doing this is to use copy_rtx. Note, however, that it unshares only a single level of rtl. Thus, if the part to be changed is not at the top level, you'll need to replace first the top level. It is not necessary for this macro to come up with a legitimate address; but often a machine-dependent strategy can generate better code.

— Macro: GO_IF_MODE_DEPENDENT_ADDRESS (addr, label)

A C statement or compound statement with a conditional goto label; executed if memory address x (an RTX) can have different meanings depending on the machine mode of the memory reference it is used for or if the address is valid for some modes but not others.

Autoincrement and autodecrement addresses typically have mode-dependent effects because the amount of the increment or decrement is the size of the operand being addressed. Some machines have other mode-dependent addresses. Many RISC machines have no mode-dependent addresses.

You may assume that addr is a valid address for the machine.

— Macro: LEGITIMATE_CONSTANT_P (x)

A C expression that is nonzero if x is a legitimate constant for an immediate operand on the target machine. You can assume that x satisfies CONSTANT_P, so you need not check this. In fact, `1' is a suitable definition for this macro on machines where anything CONSTANT_P is valid.

— Target Hook: rtx TARGET_DELEGITIMIZE_ADDRESS (rtx x)

This hook is used to undo the possibly obfuscating effects of the LEGITIMIZE_ADDRESS and LEGITIMIZE_RELOAD_ADDRESS target macros. Some backend implementations of these macros wrap symbol references inside an UNSPEC rtx to represent PIC or similar addressing modes. This target hook allows GCC's optimizers to understand the semantics of these opaque UNSPECs by converting them back into their original form.

— Target Hook: bool TARGET_CANNOT_FORCE_CONST_MEM (rtx x)

This hook should return true if x is of a form that cannot (or should not) be spilled to the constant pool. The default version of this hook returns false.

The primary reason to define this hook is to prevent reload from deciding that a non-legitimate constant would be better reloaded from the constant pool instead of spilling and reloading a register holding the constant. This restriction is often true of addresses of TLS symbols for various targets.

— Target Hook: bool TARGET_USE_BLOCKS_FOR_CONSTANT_P (enum machine_mode mode, const_rtx x)

This hook should return true if pool entries for constant x can be placed in an object_block structure. mode is the mode of x.

The default version returns false for all constants.

— Target Hook: tree TARGET_BUILTIN_RECIPROCAL (unsigned fn, bool md_fn, bool sqrt)

This hook should return the DECL of a function that implements reciprocal of the builtin function with builtin function code fn, or NULL_TREE if such a function is not available. md_fn is true when fn is a code of a machine-dependent builtin function. When sqrt is true, additional optimizations that apply only to the reciprocal of a square root function are performed, and only reciprocals of sqrt function are valid.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_MASK_FOR_LOAD (void)

This hook should return the DECL of a function f that given an address addr as an argument returns a mask m that can be used to extract from two vectors the relevant data that resides in addr in case addr is not properly aligned.

The autovectorizer, when vectorizing a load operation from an address addr that may be unaligned, will generate two vector loads from the two aligned addresses around addr. It then generates a REALIGN_LOAD operation to extract the relevant data from the two loaded vectors. The first two arguments to REALIGN_LOAD, v1 and v2, are the two vectors, each of size VS, and the third argument, OFF, defines how the data will be extracted from these two vectors: if OFF is 0, then the returned vector is v2; otherwise, the returned vector is composed from the last VS-OFF elements of v1 concatenated to the first OFF elements of v2.

If this hook is defined, the autovectorizer will generate a call to f (using the DECL tree that this hook returns) and will use the return value of f as the argument OFF to REALIGN_LOAD. Therefore, the mask m returned by f should comply with the semantics expected by REALIGN_LOAD described above. If this hook is not defined, then addr will be used as the argument OFF to REALIGN_LOAD, in which case the low log2(VS) − 1 bits of addr will be considered.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_EVEN (tree x)

This hook should return the DECL of a function f that implements widening multiplication of the even elements of two input vectors of type x.

If this hook is defined, the autovectorizer will use it along with the TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_ODD target hook when vectorizing widening multiplication in cases that the order of the results does not have to be preserved (e.g. used only by a reduction computation). Otherwise, the widen_mult_hi/lo idioms will be used.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_ODD (tree x)

This hook should return the DECL of a function f that implements widening multiplication of the odd elements of two input vectors of type x.

If this hook is defined, the autovectorizer will use it along with the TARGET_VECTORIZE_BUILTIN_MUL_WIDEN_EVEN target hook when vectorizing widening multiplication in cases that the order of the results does not have to be preserved (e.g. used only by a reduction computation). Otherwise, the widen_mult_hi/lo idioms will be used.

— Target Hook: int TARGET_VECTORIZE_BUILTIN_VECTORIZATION_COST (bool runtime_test)

Returns the cost to be added to the overhead involved with executing the vectorized version of a loop.

— Target Hook: bool TARGET_VECTORIZE_VECTOR_ALIGNMENT_REACHABLE (const_tree type, bool is_packed)

Return true if vector alignment is reachable (by peeling N iterations) for the given type.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_VEC_PERM (tree type, tree *mask_element_type)

Target builtin that implements vector permute.

— Target Hook: bool TARGET_VECTORIZE_BUILTIN_VEC_PERM_OK (tree vec_type, tree mask)

Return true if a vector created for builtin_vec_perm is valid.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_CONVERSION (unsigned code, tree type)

This hook should return the DECL of a function that implements conversion of the input vector of type type. If type is an integral type, the result of the conversion is a vector of floating-point type of the same size. If type is a floating-point type, the result of the conversion is a vector of integral type of the same size. The value of code is one of the enumerators in enum tree_code and specifies how the conversion is to be applied (truncation, rounding, etc.).

If this hook is defined, the autovectorizer will use the TARGET_VECTORIZE_BUILTIN_CONVERSION target hook when vectorizing conversion. Otherwise, it will return NULL_TREE.

— Target Hook: tree TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION (tree fndecl, tree vec_type_out, tree vec_type_in)

This hook should return the decl of a function that implements the vectorized variant of the builtin function with builtin function code code or NULL_TREE if such a function is not available. The value of fndecl is the builtin function declaration. The return type of the vectorized function shall be of vector type vec_type_out and the argument types should be vec_type_in.

— Target Hook: bool TARGET_SUPPORT_VECTOR_MISALIGNMENT (enum machine_mode mode, const_tree type, int misalignment, bool is_packed)

This hook should return true if the target supports misaligned vector store/load of a specific factor denoted in the misalignment parameter. The vector store/load should be of machine mode mode and the elements in the vectors should be of type type. is_packed parameter is true if the memory access is defined in a packed struct.