--- /dev/null
+/*{{{ Comment */
+
+/* Definitions of FR30 target.
+ Copyright (C) 1998, 1999 Free Software Foundation, Inc.
+ Contributed by Cygnus Solutions.
+
+This file is part of GNU CC.
+
+GNU CC is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
+
+GNU CC is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with GNU CC; see the file COPYING. If not, write to
+the Free Software Foundation, 59 Temple Place - Suite 330,
+Boston, MA 02111-1307, USA. */
+
+/*}}}*/ \f
+/*{{{ Includes */
+
+/* Set up System V.4 (aka ELF) defaults. */
+#include "svr4.h"
+
+/* Include prototyping macros */
+#include "gansidecl.h"
+
+/*}}}*/ \f
+/*{{{ Forward strcuture declarations for use in prototypes. */
+
+#ifdef BUFSIZ /* stdio.h has been included, ok to use FILE * */
+#define STDIO_PROTO(ARGS) PROTO(ARGS)
+#else
+#define STDIO_PROTO(ARGS) ()
+#endif
+
+#ifndef RTX_CODE
+struct rtx_def;
+#define Rtx struct rtx_def *
+#else
+#define Rtx rtx
+#endif
+
+#ifndef TREE_CODE
+union tree_node;
+#define Tree union tree_node *
+#else
+#define Tree tree
+#endif
+
+#ifndef HAVE_MACHINE_MODES
+#include "hwint.h"
+#include "machmode.h"
+#endif
+
+#define Mmode enum machine_mode
+
+/*}}}*/ \f
+/*{{{ Driver configuration */
+
+/* A C expression which determines whether the option `-CHAR' takes arguments.
+ The value should be the number of arguments that option takes-zero, for many
+ options.
+
+ By default, this macro is defined to handle the standard options properly.
+ You need not define it unless you wish to add additional options which take
+ arguments.
+
+ Defined in svr4.h. */
+#undef SWITCH_TAKES_ARG
+
+/* A C expression which determines whether the option `-NAME' takes arguments.
+ The value should be the number of arguments that option takes-zero, for many
+ options. This macro rather than `SWITCH_TAKES_ARG' is used for
+ multi-character option names.
+
+ By default, this macro is defined as `DEFAULT_WORD_SWITCH_TAKES_ARG', which
+ handles the standard options properly. You need not define
+ `WORD_SWITCH_TAKES_ARG' unless you wish to add additional options which take
+ arguments. Any redefinition should call `DEFAULT_WORD_SWITCH_TAKES_ARG' and
+ then check for additional options.
+
+ Defined in svr4.h. */
+#undef WORD_SWITCH_TAKES_ARG
+
+/*}}}*/ \f
+/*{{{ Run-time target specifications */
+
+#undef ASM_SPEC
+#define ASM_SPEC "%{v}"
+
+/* Define this to be a string constant containing `-D' options to define the
+ predefined macros that identify this machine and system. These macros will
+ be predefined unless the `-ansi' option is specified. */
+
+#define CPP_PREDEFINES "-Dfr30 -D__fr30__ -Amachine(fr30)"
+
+/* Use LDI:20 instead of LDI:32 to load addresses. */
+#define TARGET_SMALL_MODEL_MASK (1 << 0)
+#define TARGET_SMALL_MODEL (target_flags & TARGET_SMALL_MODEL_MASK)
+
+#define TARGET_DEFAULT 0
+
+/* This declaration should be present. */
+extern int target_flags;
+
+#define TARGET_SWITCHES \
+{ \
+ { "small-model", TARGET_SMALL_MODEL_MASK, "Assume small address space" }, \
+ { "no-small-model", - TARGET_SMALL_MODEL_MASK, "" }, \
+ { "no-lsim", 0, "" }, \
+ { "", TARGET_DEFAULT } \
+}
+
+#define TARGET_VERSION fprintf (stderr, " (fr30)");
+
+/* Define this macro if debugging can be performed even without a frame
+ pointer. If this macro is defined, GNU CC will turn on the
+ `-fomit-frame-pointer' option whenever `-O' is specified. */
+#define CAN_DEBUG_WITHOUT_FP
+
+#undef STARTFILE_SPEC
+#define STARTFILE_SPEC "crt0.o%s crti.o%s crtbegin.o%s"
+
+/* Include the OS stub library, so that the code can be simulated.
+ This is not the right way to do this. Ideally this kind of thing
+ should be done in the linker script - but I have not worked out how
+ to specify the location of a linker script in a gcc command line yet... */
+#undef ENDFILE_SPEC
+#define ENDFILE_SPEC "%{!mno-lsim:-lsim} crtend.o%s crtn.o%s"
+
+/*}}}*/ \f
+/*{{{ Storage Layout */
+
+/* Define this macro to have the value 1 if the most significant bit in a byte
+ has the lowest number; otherwise define it to have the value zero. This
+ means that bit-field instructions count from the most significant bit. If
+ the machine has no bit-field instructions, then this must still be defined,
+ but it doesn't matter which value it is defined to. This macro need not be
+ a constant.
+
+ This macro does not affect the way structure fields are packed into bytes or
+ words; that is controlled by `BYTES_BIG_ENDIAN'. */
+#define BITS_BIG_ENDIAN 1
+
+/* Define this macro to have the value 1 if the most significant byte in a word
+ has the lowest number. This macro need not be a constant. */
+#define BYTES_BIG_ENDIAN 1
+
+/* Define this macro to have the value 1 if, in a multiword object, the most
+ significant word has the lowest number. This applies to both memory
+ locations and registers; GNU CC fundamentally assumes that the order of
+ words in memory is the same as the order in registers. This macro need not
+ be a constant. */
+#define WORDS_BIG_ENDIAN 1
+
+/* Define this macro to be the number of bits in an addressable storage unit
+ (byte); normally 8. */
+#define BITS_PER_UNIT 8
+
+/* Number of bits in a word; normally 32. */
+#define BITS_PER_WORD 32
+
+/* Number of storage units in a word; normally 4. */
+#define UNITS_PER_WORD 4
+
+/* Width of a pointer, in bits. You must specify a value no wider than the
+ width of `Pmode'. If it is not equal to the width of `Pmode', you must
+ define `POINTERS_EXTEND_UNSIGNED'. */
+#define POINTER_SIZE 32
+
+/* A macro to update MODE and UNSIGNEDP when an object whose type is TYPE and
+ which has the specified mode and signedness is to be stored in a register.
+ This macro is only called when TYPE is a scalar type.
+
+ On most RISC machines, which only have operations that operate on a full
+ register, define this macro to set M to `word_mode' if M is an integer mode
+ narrower than `BITS_PER_WORD'. In most cases, only integer modes should be
+ widened because wider-precision floating-point operations are usually more
+ expensive than their narrower counterparts.
+
+ For most machines, the macro definition does not change UNSIGNEDP. However,
+ some machines, have instructions that preferentially handle either signed or
+ unsigned quantities of certain modes. For example, on the DEC Alpha, 32-bit
+ loads from memory and 32-bit add instructions sign-extend the result to 64
+ bits. On such machines, set UNSIGNEDP according to which kind of extension
+ is more efficient.
+
+ Do not define this macro if it would never modify MODE. */
+#define PROMOTE_MODE(MODE,UNSIGNEDP,TYPE) \
+do { \
+ if (GET_MODE_CLASS (MODE) == MODE_INT \
+ && GET_MODE_SIZE (MODE) < 4) \
+ (MODE) = SImode; \
+} while (0)
+
+/* Normal alignment required for function parameters on the stack, in bits.
+ All stack parameters receive at least this much alignment regardless of data
+ type. On most machines, this is the same as the size of an integer. */
+#define PARM_BOUNDARY 32
+
+/* Define this macro if you wish to preserve a certain alignment for the stack
+ pointer. The definition is a C expression for the desired alignment
+ (measured in bits).
+
+ If `PUSH_ROUNDING' is not defined, the stack will always be aligned to the
+ specified boundary. If `PUSH_ROUNDING' is defined and specifies a less
+ strict alignment than `STACK_BOUNDARY', the stack may be momentarily
+ unaligned while pushing arguments. */
+#define STACK_BOUNDARY 32
+
+/* Alignment required for a function entry point, in bits. */
+#define FUNCTION_BOUNDARY 32
+
+/* Biggest alignment that any data type can require on this machine,
+ in bits. */
+#define BIGGEST_ALIGNMENT 32
+
+/* If defined, a C expression to compute the alignment for a static variable.
+ TYPE is the data type, and ALIGN is the alignment that the object
+ would ordinarily have. The value of this macro is used instead of that
+ alignment to align the object.
+
+ If this macro is not defined, then ALIGN is used.
+
+ One use of this macro is to increase alignment of medium-size data to make
+ it all fit in fewer cache lines. Another is to cause character arrays to be
+ word-aligned so that `strcpy' calls that copy constants to character arrays
+ can be done inline. */
+#define DATA_ALIGNMENT(TYPE, ALIGN) \
+ (TREE_CODE (TYPE) == ARRAY_TYPE \
+ && TYPE_MODE (TREE_TYPE (TYPE)) == QImode \
+ && (ALIGN) < BITS_PER_WORD ? BITS_PER_WORD : (ALIGN))
+
+/* If defined, a C expression to compute the alignment given to a constant that
+ is being placed in memory. CONSTANT is the constant and ALIGN is the
+ alignment that the object would ordinarily have. The value of this macro is
+ used instead of that alignment to align the object.
+
+ If this macro is not defined, then ALIGN is used.
+
+ The typical use of this macro is to increase alignment for string constants
+ to be word aligned so that `strcpy' calls that copy constants can be done
+ inline. */
+#define CONSTANT_ALIGNMENT(EXP, ALIGN) \
+ (TREE_CODE (EXP) == STRING_CST \
+ && (ALIGN) < BITS_PER_WORD ? BITS_PER_WORD : (ALIGN))
+
+/* Alignment in bits to be given to a structure bit field that follows an empty
+ field such as `int : 0;'.
+
+ Note that `PCC_BITFIELD_TYPE_MATTERS' also affects the alignment that
+ results from an empty field. */
+/* #define EMPTY_FIELD_BOUNDARY */
+
+/* Number of bits which any structure or union's size must be a multiple of.
+ Each structure or union's size is rounded up to a multiple of this.
+
+ If you do not define this macro, the default is the same as `BITS_PER_UNIT'. */
+/* #define STRUCTURE_SIZE_BOUNDARY */
+
+/* Define this macro to be the value 1 if instructions will fail to work if
+ given data not on the nominal alignment. If instructions will merely go
+ slower in that case, define this macro as 0. */
+#define STRICT_ALIGNMENT 1
+
+/* Define this if you wish to imitate the way many other C compilers handle
+ alignment of bitfields and the structures that contain them.
+
+ The behavior is that the type written for a bitfield (`int', `short', or
+ other integer type) imposes an alignment for the entire structure, as if the
+ structure really did contain an ordinary field of that type. In addition,
+ the bitfield is placed within the structure so that it would fit within such
+ a field, not crossing a boundary for it.
+
+ Thus, on most machines, a bitfield whose type is written as `int' would not
+ cross a four-byte boundary, and would force four-byte alignment for the
+ whole structure. (The alignment used may not be four bytes; it is
+ controlled by the other alignment parameters.)
+
+ If the macro is defined, its definition should be a C expression; a nonzero
+ value for the expression enables this behavior.
+
+ Note that if this macro is not defined, or its value is zero, some bitfields
+ may cross more than one alignment boundary. The compiler can support such
+ references if there are `insv', `extv', and `extzv' insns that can directly
+ reference memory.
+
+ The other known way of making bitfields work is to define
+ `STRUCTURE_SIZE_BOUNDARY' as large as `BIGGEST_ALIGNMENT'. Then every
+ structure can be accessed with fullwords.
+
+ Unless the machine has bitfield instructions or you define
+ `STRUCTURE_SIZE_BOUNDARY' that way, you must define
+ `PCC_BITFIELD_TYPE_MATTERS' to have a nonzero value.
+
+ If your aim is to make GNU CC use the same conventions for laying out
+ bitfields as are used by another compiler, here is how to investigate what
+ the other compiler does. Compile and run this program:
+
+ struct foo1
+ {
+ char x;
+ char :0;
+ char y;
+ };
+
+ struct foo2
+ {
+ char x;
+ int :0;
+ char y;
+ };
+
+ main ()
+ {
+ printf ("Size of foo1 is %d\n",
+ sizeof (struct foo1));
+ printf ("Size of foo2 is %d\n",
+ sizeof (struct foo2));
+ exit (0);
+ }
+
+ If this prints 2 and 5, then the compiler's behavior is what you would get
+ from `PCC_BITFIELD_TYPE_MATTERS'.
+
+ Defined in svr4.h. */
+#define PCC_BITFIELD_TYPE_MATTERS 1
+
+/* A code distinguishing the floating point format of the target machine.
+ There are three defined values:
+
+ IEEE_FLOAT_FORMAT'
+ This code indicates IEEE floating point. It is the default;
+ there is no need to define this macro when the format is IEEE.
+
+ VAX_FLOAT_FORMAT'
+ This code indicates the peculiar format used on the Vax.
+
+ UNKNOWN_FLOAT_FORMAT'
+ This code indicates any other format.
+
+ The value of this macro is compared with `HOST_FLOAT_FORMAT'
+ to determine whether the target machine has the same format as
+ the host machine. If any other formats are actually in use on supported
+ machines, new codes should be defined for them.
+
+ The ordering of the component words of floating point values stored in
+ memory is controlled by `FLOAT_WORDS_BIG_ENDIAN' for the target machine and
+ `HOST_FLOAT_WORDS_BIG_ENDIAN' for the host. */
+#define TARGET_FLOAT_FORMAT IEEE_FLOAT_FORMAT
+
+/* GNU CC supports two ways of implementing C++ vtables: traditional or with
+ so-called "thunks". The flag `-fvtable-thunk' chooses between them. Define
+ this macro to be a C expression for the default value of that flag. If
+ `DEFAULT_VTABLE_THUNKS' is 0, GNU CC uses the traditional implementation by
+ default. The "thunk" implementation is more efficient (especially if you
+ have provided an implementation of `ASM_OUTPUT_MI_THUNK', but is not binary
+ compatible with code compiled using the traditional implementation. If you
+ are writing a new ports, define `DEFAULT_VTABLE_THUNKS' to 1.
+
+ If you do not define this macro, the default for `-fvtable-thunk' is 0. */
+#define DEFAULT_VTABLE_THUNKS 1
+
+/*}}}*/ \f
+/*{{{ Layout of Source Language Data Types */
+
+#define CHAR_TYPE_SIZE 8
+#define SHORT_TYPE_SIZE 16
+#define INT_TYPE_SIZE 32
+#define LONG_TYPE_SIZE 32
+#define LONG_LONG_TYPE_SIZE 64
+#define FLOAT_TYPE_SIZE 32
+#define DOUBLE_TYPE_SIZE 64
+#define LONG_DOUBLE_TYPE_SIZE 64
+
+/* An expression whose value is 1 or 0, according to whether the type `char'
+ should be signed or unsigned by default. The user can always override this
+ default with the options `-fsigned-char' and `-funsigned-char'. */
+#define DEFAULT_SIGNED_CHAR 1
+
+#define TARGET_BELL 0x7 /* '\a' */
+#define TARGET_BS 0x8 /* '\b' */
+#define TARGET_TAB 0x9 /* '\t' */
+#define TARGET_NEWLINE 0xa /* '\n' */
+#define TARGET_VT 0xb /* '\v' */
+#define TARGET_FF 0xc /* '\f' */
+#define TARGET_CR 0xd /* '\r' */
+
+/*}}}*/ \f
+/*{{{ REGISTER BASICS */
+
+/* Number of hardware registers known to the compiler. They receive numbers 0
+ through `FIRST_PSEUDO_REGISTER-1'; thus, the first pseudo register's number
+ really is assigned the number `FIRST_PSEUDO_REGISTER'. */
+#define FIRST_PSEUDO_REGISTER 21
+
+/* Fixed register assignments: */
+
+/* Here we do a BAD THING - reserve a register for use by the machine
+ description file. There are too many places in compiler where it
+ assumes that it can issue a branch or jump instruction without
+ providing a scratch register for it, and reload just cannot cope, so
+ we keep a register back for these situations. */
+#define COMPILER_SCRATCH_REGISTER 0
+
+/* The register that contains the result of a function call. */
+#define RETURN_VALUE_REGNUM 4
+
+/* The first register that can contain the arguments to a function. */
+#define FIRST_ARG_REGNUM 4
+
+/* A call-used register that can be used during the function prologue. */
+#define PROLOGUE_TMP_REGNUM COMPILER_SCRATCH_REGISTER
+
+/* Register numbers used for passing a function's static chain pointer. If
+ register windows are used, the register number as seen by the called
+ function is `STATIC_CHAIN_INCOMING_REGNUM', while the register number as
+ seen by the calling function is `STATIC_CHAIN_REGNUM'. If these registers
+ are the same, `STATIC_CHAIN_INCOMING_REGNUM' need not be defined.
+
+ The static chain register need not be a fixed register.
+
+ If the static chain is passed in memory, these macros should not be defined;
+ instead, the next two macros should be defined. */
+#define STATIC_CHAIN_REGNUM 12
+/* #define STATIC_CHAIN_INCOMING_REGNUM */
+
+/* An FR30 specific hardware register. */
+#define ACCUMULATOR_REGNUM 13
+
+/* The register number of the frame pointer register, which is used to access
+ automatic variables in the stack frame. On some machines, the hardware
+ determines which register this is. On other machines, you can choose any
+ register you wish for this purpose. */
+#define FRAME_POINTER_REGNUM 14
+
+/* The register number of the stack pointer register, which must also be a
+ fixed register according to `FIXED_REGISTERS'. On most machines, the
+ hardware determines which register this is. */
+#define STACK_POINTER_REGNUM 15
+
+/* The following a fake hard registers that describe some of the dedicated
+ registers on the FR30. */
+#define CONDITION_CODE_REGNUM 16
+#define RETURN_POINTER_REGNUM 17
+#define MD_HIGH_REGNUM 18
+#define MD_LOW_REGNUM 19
+
+/* An initializer that says which registers are used for fixed purposes all
+ throughout the compiled code and are therefore not available for general
+ allocation. These would include the stack pointer, the frame pointer
+ (except on machines where that can be used as a general register when no
+ frame pointer is needed), the program counter on machines where that is
+ considered one of the addressable registers, and any other numbered register
+ with a standard use.
+
+ This information is expressed as a sequence of numbers, separated by commas
+ and surrounded by braces. The Nth number is 1 if register N is fixed, 0
+ otherwise.
+
+ The table initialized from this macro, and the table initialized by the
+ following one, may be overridden at run time either automatically, by the
+ actions of the macro `CONDITIONAL_REGISTER_USAGE', or by the user with the
+ command options `-ffixed-REG', `-fcall-used-REG' and `-fcall-saved-REG'. */
+#define FIXED_REGISTERS \
+ { 1, 0, 0, 0, 0, 0, 0, 0, /* 0 - 7 */ \
+ 0, 0, 0, 0, 0, 0, 0, 1, /* 8 - 15 */ \
+ 1, 1, 1, 1, 1 } /* 16 - 20 */
+
+/* XXX - MDL and MDH set as fixed for now - this is until I can get the
+ mul patterns working. */
+
+/* Like `FIXED_REGISTERS' but has 1 for each register that is clobbered (in
+ general) by function calls as well as for fixed registers. This macro
+ therefore identifies the registers that are not available for general
+ allocation of values that must live across function calls.
+
+ If a register has 0 in `CALL_USED_REGISTERS', the compiler automatically
+ saves it on function entry and restores it on function exit, if the register
+ is used within the function. */
+#define CALL_USED_REGISTERS \
+ { 1, 1, 1, 1, 1, 1, 1, 1, /* 0 - 7 */ \
+ 0, 0, 0, 0, 1, 1, 0, 1, /* 8 - 15 */ \
+ 1, 1, 1, 1, 1 } /* 16 - 20 */
+
+/* A C initializer containing the assembler's names for the machine registers,
+ each one as a C string constant. This is what translates register numbers
+ in the compiler into assembler language. */
+#define REGISTER_NAMES \
+{ "r0", "r1", "r2", "r3", "r4", "r5", "r6", "r7", \
+ "r8", "r9", "r10", "r11", "r12", "ac", "fp", "sp", \
+ "cc", "rp", "mdh", "mdl", "ap" \
+}
+
+/* If defined, a C initializer for an array of structures containing a name and
+ a register number. This macro defines additional names for hard registers,
+ thus allowing the `asm' option in declarations to refer to registers using
+ alternate names. */
+#define ADDITIONAL_REGISTER_NAMES \
+{ \
+ {"r13", 13}, {"r14", 14}, {"r15", 15}, {"usp", 15}, {"ps", 16}\
+}
+
+/*}}}*/ \f
+/*{{{ How Values Fit in Registers */
+
+/* A C expression for the number of consecutive hard registers, starting at
+ register number REGNO, required to hold a value of mode MODE. */
+
+#define HARD_REGNO_NREGS(REGNO, MODE) \
+ ((GET_MODE_SIZE (MODE) + UNITS_PER_WORD - 1) / UNITS_PER_WORD)
+
+/* A C expression that is nonzero if it is permissible to store a value of mode
+ MODE in hard register number REGNO (or in several registers starting with
+ that one). */
+
+#define HARD_REGNO_MODE_OK(REGNO, MODE) 1
+
+/* A C expression that is nonzero if it is desirable to choose register
+ allocation so as to avoid move instructions between a value of mode MODE1
+ and a value of mode MODE2.
+
+ If `HARD_REGNO_MODE_OK (R, MODE1)' and `HARD_REGNO_MODE_OK (R, MODE2)' are
+ ever different for any R, then `MODES_TIEABLE_P (MODE1, MODE2)' must be
+ zero. */
+#define MODES_TIEABLE_P(MODE1, MODE2) 1
+
+/* Define this macro if the compiler should avoid copies to/from CCmode
+ registers. You should only define this macro if support fo copying to/from
+ CCmode is incomplete. */
+/* #define AVOID_CCMODE_COPIES */
+
+/*}}}*/ \f
+/*{{{ Register Classes */
+
+/* An enumeral type that must be defined with all the register class names as
+ enumeral values. `NO_REGS' must be first. `ALL_REGS' must be the last
+ register class, followed by one more enumeral value, `LIM_REG_CLASSES',
+ which is not a register class but rather tells how many classes there are.
+
+ Each register class has a number, which is the value of casting the class
+ name to type `int'. The number serves as an index in many of the tables
+ described below. */
+enum reg_class
+{
+ NO_REGS,
+ MULTIPLY_32_REG, /* the MDL register as used by the MULH, MULUH insns */
+ MULTIPLY_64_REG, /* the MDH,MDL register pair as used by MUL and MULU */
+ LOW_REGS, /* registers 0 through 7 */
+ HIGH_REGS, /* registers 8 through 15 */
+ REAL_REGS, /* ie all the general hardware registers on the FR30 */
+ ALL_REGS,
+ LIM_REG_CLASSES
+};
+
+#define GENERAL_REGS REAL_REGS
+#define N_REG_CLASSES ((int) LIM_REG_CLASSES)
+
+/* An initializer containing the names of the register classes as C string
+ constants. These names are used in writing some of the debugging dumps. */
+#define REG_CLASS_NAMES \
+{ \
+ "NO_REGS", \
+ "MULTIPLY_32_REG", \
+ "MULTIPLY_64_REG", \
+ "LOW_REGS", \
+ "HIGH_REGS", \
+ "REAL_REGS", \
+ "ALL_REGS" \
+ }
+
+/* An initializer containing the contents of the register classes, as integers
+ which are bit masks. The Nth integer specifies the contents of class N.
+ The way the integer MASK is interpreted is that register R is in the class
+ if `MASK & (1 << R)' is 1.
+
+ When the machine has more than 32 registers, an integer does not suffice.
+ Then the integers are replaced by sub-initializers, braced groupings
+ containing several integers. Each sub-initializer must be suitable as an
+ initializer for the type `HARD_REG_SET' which is defined in
+ `hard-reg-set.h'. */
+#define REG_CLASS_CONTENTS \
+{ \
+ 0, \
+ 1 << MD_LOW_REGNUM, \
+ (1 << MD_LOW_REGNUM) | (1 << MD_HIGH_REGNUM), \
+ (1 << 8) - 1, \
+ ((1 << 8) - 1) << 8, \
+ (1 << CONDITION_CODE_REGNUM) - 1, \
+ (1 << FIRST_PSEUDO_REGISTER) - 1 \
+}
+
+/* A C expression whose value is a register class containing hard register
+ REGNO. In general there is more than one such class; choose a class which
+ is "minimal", meaning that no smaller class also contains the register. */
+#define REGNO_REG_CLASS(REGNO) \
+ ( (REGNO) < 8 ? LOW_REGS \
+ : (REGNO) < CONDITION_CODE_REGNUM ? HIGH_REGS \
+ : (REGNO) == MD_LOW_REGNUM ? MULTIPLY_32_REG \
+ : (REGNO) == MD_HIGH_REGNUM ? MULTIPLY_64_REG \
+ : ALL_REGS)
+
+/* A macro whose definition is the name of the class to which a valid base
+ register must belong. A base register is one used in an address which is
+ the register value plus a displacement. */
+#define BASE_REG_CLASS REAL_REGS
+
+/* A macro whose definition is the name of the class to which a valid index
+ register must belong. An index register is one used in an address where its
+ value is either multiplied by a scale factor or added to another register
+ (as well as added to a displacement). */
+#define INDEX_REG_CLASS REAL_REGS
+
+/* A C expression which defines the machine-dependent operand constraint
+ letters for register classes. If CHAR is such a letter, the value should be
+ the register class corresponding to it. Otherwise, the value should be
+ `NO_REGS'. The register letter `r', corresponding to class `GENERAL_REGS',
+ will not be passed to this macro; you do not need to handle it.
+
+ The following letters are unavailable, due to being used as
+ constraints:
+ '0'..'9'
+ '<', '>'
+ 'E', 'F', 'G', 'H'
+ 'I', 'J', 'K', 'L', 'M', 'N', 'O', 'P'
+ 'Q', 'R', 'S', 'T', 'U'
+ 'V', 'X'
+ 'g', 'i', 'm', 'n', 'o', 'p', 'r', 's' */
+
+#define REG_CLASS_FROM_LETTER(CHAR) \
+ ( (CHAR) == 'd' ? MULTIPLY_64_REG \
+ : (CHAR) == 'e' ? MULTIPLY_32_REG \
+ : (CHAR) == 'h' ? HIGH_REGS \
+ : (CHAR) == 'l' ? LOW_REGS \
+ : (CHAR) == 'a' ? ALL_REGS \
+ : NO_REGS)
+
+/* A C expression which is nonzero if register number NUM is suitable for use
+ as a base register in operand addresses. It may be either a suitable hard
+ register or a pseudo register that has been allocated such a hard register. */
+#define REGNO_OK_FOR_BASE_P(NUM) 1
+
+/* A C expression which is nonzero if register number NUM is suitable for use
+ as an index register in operand addresses. It may be either a suitable hard
+ register or a pseudo register that has been allocated such a hard register.
+
+ The difference between an index register and a base register is that the
+ index register may be scaled. If an address involves the sum of two
+ registers, neither one of them scaled, then either one may be labeled the
+ "base" and the other the "index"; but whichever labeling is used must fit
+ the machine's constraints of which registers may serve in each capacity.
+ The compiler will try both labelings, looking for one that is valid, and
+ will reload one or both registers only if neither labeling works. */
+#define REGNO_OK_FOR_INDEX_P(NUM) 1
+
+/* A C expression that places additional restrictions on the register class to
+ use when it is necessary to copy value X into a register in class CLASS.
+ The value is a register class; perhaps CLASS, or perhaps another, smaller
+ class. On many machines, the following definition is safe:
+
+ #define PREFERRED_RELOAD_CLASS(X,CLASS) CLASS
+
+ Sometimes returning a more restrictive class makes better code. For
+ example, on the 68000, when X is an integer constant that is in range for a
+ `moveq' instruction, the value of this macro is always `DATA_REGS' as long
+ as CLASS includes the data registers. Requiring a data register guarantees
+ that a `moveq' will be used.
+
+ If X is a `const_double', by returning `NO_REGS' you can force X into a
+ memory constant. This is useful on certain machines where immediate
+ floating values cannot be loaded into certain kinds of registers. */
+#define PREFERRED_RELOAD_CLASS(X, CLASS) CLASS
+
+/* Like `PREFERRED_RELOAD_CLASS', but for output reloads instead of input
+ reloads. If you don't define this macro, the default is to use CLASS,
+ unchanged. */
+/* #define PREFERRED_OUTPUT_RELOAD_CLASS(X, CLASS) */
+
+/* A C expression that places additional restrictions on the register class to
+ use when it is necessary to be able to hold a value of mode MODE in a reload
+ register for which class CLASS would ordinarily be used.
+
+ Unlike `PREFERRED_RELOAD_CLASS', this macro should be used when there are
+ certain modes that simply can't go in certain reload classes.
+
+ The value is a register class; perhaps CLASS, or perhaps another, smaller
+ class.
+
+ Don't define this macro unless the target machine has limitations which
+ require the macro to do something nontrivial. */
+/* #define LIMIT_RELOAD_CLASS(MODE, CLASS) */
+
+/* Many machines have some registers that cannot be copied directly to or from
+ memory or even from other types of registers. An example is the `MQ'
+ register, which on most machines, can only be copied to or from general
+ registers, but not memory. Some machines allow copying all registers to and
+ from memory, but require a scratch register for stores to some memory
+ locations (e.g., those with symbolic address on the RT, and those with
+ certain symbolic address on the Sparc when compiling PIC). In some cases,
+ both an intermediate and a scratch register are required.
+
+ You should define these macros to indicate to the reload phase that it may
+ need to allocate at least one register for a reload in addition to the
+ register to contain the data. Specifically, if copying X to a register
+ CLASS in MODE requires an intermediate register, you should define
+ `SECONDARY_INPUT_RELOAD_CLASS' to return the largest register class all of
+ whose registers can be used as intermediate registers or scratch registers.
+
+ If copying a register CLASS in MODE to X requires an intermediate or scratch
+ register, `SECONDARY_OUTPUT_RELOAD_CLASS' should be defined to return the
+ largest register class required. If the requirements for input and output
+ reloads are the same, the macro `SECONDARY_RELOAD_CLASS' should be used
+ instead of defining both macros identically.
+
+ The values returned by these macros are often `GENERAL_REGS'. Return
+ `NO_REGS' if no spare register is needed; i.e., if X can be directly copied
+ to or from a register of CLASS in MODE without requiring a scratch register.
+ Do not define this macro if it would always return `NO_REGS'.
+
+ If a scratch register is required (either with or without an intermediate
+ register), you should define patterns for `reload_inM' or `reload_outM', as
+ required. These patterns, which will normally be implemented with a
+ `define_expand', should be similar to the `movM' patterns, except that
+ operand 2 is the scratch register.
+
+ Define constraints for the reload register and scratch register that contain
+ a single register class. If the original reload register (whose class is
+ CLASS) can meet the constraint given in the pattern, the value returned by
+ these macros is used for the class of the scratch register. Otherwise, two
+ additional reload registers are required. Their classes are obtained from
+ the constraints in the insn pattern.
+
+ X might be a pseudo-register or a `subreg' of a pseudo-register, which could
+ either be in a hard register or in memory. Use `true_regnum' to find out;
+ it will return -1 if the pseudo is in memory and the hard register number if
+ it is in a register.
+
+ These macros should not be used in the case where a particular class of
+ registers can only be copied to memory and not to another class of
+ registers. In that case, secondary reload registers are not needed and
+ would not be helpful. Instead, a stack location must be used to perform the
+ copy and the `movM' pattern should use memory as a intermediate storage.
+ This case often occurs between floating-point and general registers. */
+/* #define SECONDARY_RELOAD_CLASS(CLASS, MODE, X) */
+/* #define SECONDARY_INPUT_RELOAD_CLASS(CLASS, MODE, X) */
+/* #define SECONDARY_OUTPUT_RELOAD_CLASS(CLASS, MODE, X) */
+
+/* Normally the compiler avoids choosing registers that have been explicitly
+ mentioned in the rtl as spill registers (these registers are normally those
+ used to pass parameters and return values). However, some machines have so
+ few registers of certain classes that there would not be enough registers to
+ use as spill registers if this were done.
+
+ Define `SMALL_REGISTER_CLASSES' to be an expression with a non-zero value on
+ these machines. When this macro has a non-zero value, the compiler allows
+ registers explicitly used in the rtl to be used as spill registers but
+ avoids extending the lifetime of these registers.
+
+ It is always safe to define this macro with a non-zero value, but if you
+ unnecessarily define it, you will reduce the amount of optimizations that
+ can be performed in some cases. If you do not define this macro with a
+ non-zero value when it is required, the compiler will run out of spill
+ registers and print a fatal error message. For most machines, you should
+ not define this macro at all. */
+/* #define SMALL_REGISTER_CLASSES */
+
+/* A C expression whose value is nonzero if pseudos that have been assigned to
+ registers of class CLASS would likely be spilled because registers of CLASS
+ are needed for spill registers.
+
+ The default value of this macro returns 1 if CLASS has exactly one register
+ and zero otherwise. On most machines, this default should be used. Only
+ define this macro to some other expression if pseudo allocated by
+ `local-alloc.c' end up in memory because their hard registers were needed
+ for spill registers. If this macro returns nonzero for those classes, those
+ pseudos will only be allocated by `global.c', which knows how to reallocate
+ the pseudo to another register. If there would not be another register
+ available for reallocation, you should not change the definition of this
+ macro since the only effect of such a definition would be to slow down
+ register allocation. */
+/* #define CLASS_LIKELY_SPILLED_P(CLASS) */
+
+/* A C expression for the maximum number of consecutive registers of
+ class CLASS needed to hold a value of mode MODE.
+
+ This is closely related to the macro `HARD_REGNO_NREGS'. In fact, the value
+ of the macro `CLASS_MAX_NREGS (CLASS, MODE)' should be the maximum value of
+ `HARD_REGNO_NREGS (REGNO, MODE)' for all REGNO values in the class CLASS.
+
+ This macro helps control the handling of multiple-word values in
+ the reload pass. */
+#define CLASS_MAX_NREGS(CLASS, MODE) HARD_REGNO_NREGS (0, MODE)
+
+/* If defined, a C expression for a class that contains registers which the
+ compiler must always access in a mode that is the same size as the mode in
+ which it loaded the register.
+
+ For the example, loading 32-bit integer or floating-point objects into
+ floating-point registers on the Alpha extends them to 64-bits. Therefore
+ loading a 64-bit object and then storing it as a 32-bit object does not
+ store the low-order 32-bits, as would be the case for a normal register.
+ Therefore, `alpha.h' defines this macro as `FLOAT_REGS'. */
+/* #define CLASS_CANNOT_CHANGE_SIZE */
+
+/*}}}*/ \f
+/*{{{ CONSTANTS */
+
+/* Return true if a value is inside a range */
+#define IN_RANGE(VALUE, LOW, HIGH) \
+ ( ((unsigned HOST_WIDE_INT)((VALUE) - (LOW))) \
+ <= ((unsigned HOST_WIDE_INT)( (HIGH) - (LOW))))
+
+/* A C expression that defines the machine-dependent operand constraint letters
+ (`I', `J', `K', .. 'P') that specify particular ranges of integer values.
+ If C is one of those letters, the expression should check that VALUE, an
+ integer, is in the appropriate range and return 1 if so, 0 otherwise. If C
+ is not one of those letters, the value should be 0 regardless of VALUE. */
+#define CONST_OK_FOR_LETTER_P(VALUE, C) \
+ ( (C) == 'I' ? IN_RANGE (VALUE, 0, 15) \
+ : (C) == 'J' ? IN_RANGE (VALUE, -16, -1) \
+ : (C) == 'K' ? IN_RANGE (VALUE, 16, 31) \
+ : (C) == 'L' ? IN_RANGE (VALUE, 0, (1 << 8) - 1) \
+ : (C) == 'M' ? IN_RANGE (VALUE, 0, (1 << 20) - 1) \
+ : (C) == 'P' ? IN_RANGE (VALUE, -(1 << 8), (1 << 8) - 1) \
+ : 0)
+
+/* A C expression that defines the machine-dependent operand constraint letters
+ (`G', `H') that specify particular ranges of `const_double' values.
+
+ If C is one of those letters, the expression should check that VALUE, an RTX
+ of code `const_double', is in the appropriate range and return 1 if so, 0
+ otherwise. If C is not one of those letters, the value should be 0
+ regardless of VALUE.
+
+ `const_double' is used for all floating-point constants and for `DImode'
+ fixed-point constants. A given letter can accept either or both kinds of
+ values. It can use `GET_MODE' to distinguish between these kinds. */
+#define CONST_DOUBLE_OK_FOR_LETTER_P(VALUE, C) 0
+
+/* A C expression that defines the optional machine-dependent constraint
+ letters (`Q', `R', `S', `T', `U') that can be used to segregate specific
+ types of operands, usually memory references, for the target machine.
+ Normally this macro will not be defined. If it is required for a particular
+ target machine, it should return 1 if VALUE corresponds to the operand type
+ represented by the constraint letter C. If C is not defined as an extra
+ constraint, the value returned should be 0 regardless of VALUE.
+
+ For example, on the ROMP, load instructions cannot have their output in r0
+ if the memory reference contains a symbolic address. Constraint letter `Q'
+ is defined as representing a memory address that does *not* contain a
+ symbolic address. An alternative is specified with a `Q' constraint on the
+ input and `r' on the output. The next alternative specifies `m' on the
+ input and a register class that does not include r0 on the output. */
+#define EXTRA_CONSTRAINT(VALUE, C) \
+ ((C) == 'Q' ? (GET_CODE (VALUE) == MEM && GET_CODE (XEXP (VALUE, 0)) == SYMBOL_REF) : 0)
+
+/*}}}*/ \f
+/*{{{ Basic Stack Layout */
+
+/* Define this macro if pushing a word onto the stack moves the stack pointer
+ to a smaller address. */
+#define STACK_GROWS_DOWNWARD 1
+
+/* Define this macro if the addresses of local variable slots are at negative
+ offsets from the frame pointer. */
+#define FRAME_GROWS_DOWNWARD 1
+
+/* Define this macro if successive arguments to a function occupy decreasing
+ addresses on the stack. */
+/* #define ARGS_GROW_DOWNWARD */
+
+/* Offset from the frame pointer to the first local variable slot to be
+ allocated.
+
+ If `FRAME_GROWS_DOWNWARD', find the next slot's offset by subtracting the
+ first slot's length from `STARTING_FRAME_OFFSET'. Otherwise, it is found by
+ adding the length of the first slot to the value `STARTING_FRAME_OFFSET'. */
+/* #define STARTING_FRAME_OFFSET -4 */
+#define STARTING_FRAME_OFFSET 0
+
+/* Offset from the stack pointer register to the first location at which
+ outgoing arguments are placed. If not specified, the default value of zero
+ is used. This is the proper value for most machines.
+
+ If `ARGS_GROW_DOWNWARD', this is the offset to the location above the first
+ location at which outgoing arguments are placed. */
+#define STACK_POINTER_OFFSET 0
+
+/* Offset from the argument pointer register to the first argument's address.
+ On some machines it may depend on the data type of the function.
+
+ If `ARGS_GROW_DOWNWARD', this is the offset to the location above the first
+ argument's address. */
+#define FIRST_PARM_OFFSET(FUNDECL) 0
+
+/* Offset from the stack pointer register to an item dynamically allocated on
+ the stack, e.g., by `alloca'.
+
+ The default value for this macro is `STACK_POINTER_OFFSET' plus the length
+ of the outgoing arguments. The default is correct for most machines. See
+ `function.c' for details. */
+/* #define STACK_DYNAMIC_OFFSET(FUNDECL) */
+
+/* A C expression whose value is RTL representing the address in a stack frame
+ where the pointer to the caller's frame is stored. Assume that FRAMEADDR is
+ an RTL expression for the address of the stack frame itself.
+
+ If you don't define this macro, the default is to return the value of
+ FRAMEADDR--that is, the stack frame address is also the address of the stack
+ word that points to the previous frame. */
+/* #define DYNAMIC_CHAIN_ADDRESS(FRAMEADDR) */
+
+/* A C expression whose value is RTL representing the value of the return
+ address for the frame COUNT steps up from the current frame, after the
+ prologue. FRAMEADDR is the frame pointer of the COUNT frame, or the frame
+ pointer of the COUNT - 1 frame if `RETURN_ADDR_IN_PREVIOUS_FRAME' is
+ defined.
+
+ The value of the expression must always be the correct address when COUNT is
+ zero, but may be `NULL_RTX' if there is not way to determine the return
+ address of other frames. */
+/* #define RETURN_ADDR_RTX(COUNT, FRAMEADDR) */
+
+/* Define this if the return address of a particular stack frame is
+ accessed from the frame pointer of the previous stack frame. */
+/* #define RETURN_ADDR_IN_PREVIOUS_FRAME */
+
+/* A C expression whose value is RTL representing the location of the incoming
+ return address at the beginning of any function, before the prologue. This
+ RTL is either a `REG', indicating that the return value is saved in `REG',
+ or a `MEM' representing a location in the stack.
+
+ You only need to define this macro if you want to support call frame
+ debugging information like that provided by DWARF 2. */
+#define INCOMING_RETURN_ADDR_RTX gen_rtx_REG (SImode, RETURN_POINTER_REGNUM)
+
+/* A C expression whose value is an integer giving the offset, in bytes, from
+ the value of the stack pointer register to the top of the stack frame at the
+ beginning of any function, before the prologue. The top of the frame is
+ defined to be the value of the stack pointer in the previous frame, just
+ before the call instruction.
+
+ You only need to define this macro if you want to support call frame
+ debugging information like that provided by DWARF 2. */
+/* #define INCOMING_FRAME_SP_OFFSET */
+
+/*}}}*/ \f
+/*{{{ Register That Address the Stack Frame. */
+
+/* On some machines the offset between the frame pointer and starting offset of
+ the automatic variables is not known until after register allocation has
+ been done (for example, because the saved registers are between these two
+ locations). On those machines, define `FRAME_POINTER_REGNUM' the number of
+ a special, fixed register to be used internally until the offset is known,
+ and define `HARD_FRAME_POINTER_REGNUM' to be actual the hard register number
+ used for the frame pointer.
+
+ You should define this macro only in the very rare circumstances when it is
+ not possible to calculate the offset between the frame pointer and the
+ automatic variables until after register allocation has been completed.
+ When this macro is defined, you must also indicate in your definition of
+ `ELIMINABLE_REGS' how to eliminate `FRAME_POINTER_REGNUM' into either
+ `HARD_FRAME_POINTER_REGNUM' or `STACK_POINTER_REGNUM'.
+
+ Do not define this macro if it would be the same as `FRAME_POINTER_REGNUM'. */
+/* #define HARD_FRAME_POINTER_REGNUM */
+
+/* The register number of the arg pointer register, which is used to access the
+ function's argument list. On some machines, this is the same as the frame
+ pointer register. On some machines, the hardware determines which register
+ this is. On other machines, you can choose any register you wish for this
+ purpose. If this is not the same register as the frame pointer register,
+ then you must mark it as a fixed register according to `FIXED_REGISTERS', or
+ arrange to be able to eliminate it. */
+#define ARG_POINTER_REGNUM 20
+
+/* The register number of the return address pointer register, which is used to
+ access the current function's return address from the stack. On some
+ machines, the return address is not at a fixed offset from the frame pointer
+ or stack pointer or argument pointer. This register can be defined to point
+ to the return address on the stack, and then be converted by
+ `ELIMINABLE_REGS' into either the frame pointer or stack pointer.
+
+ Do not define this macro unless there is no other way to get the return
+ address from the stack. */
+/* #define RETURN_ADDRESS_POINTER_REGNUM */
+
+/* If the static chain is passed in memory, these macros provide rtx giving
+ `mem' expressions that denote where they are stored. `STATIC_CHAIN' and
+ `STATIC_CHAIN_INCOMING' give the locations as seen by the calling and called
+ functions, respectively. Often the former will be at an offset from the
+ stack pointer and the latter at an offset from the frame pointer.
+
+ The variables `stack_pointer_rtx', `frame_pointer_rtx', and
+ `arg_pointer_rtx' will have been initialized prior to the use of these
+ macros and should be used to refer to those items.
+
+ If the static chain is passed in a register, the two previous
+ macros should be defined instead. */
+/* #define STATIC_CHAIN */
+/* #define STATIC_CHAIN_INCOMING */
+
+/*}}}*/ \f
+/*{{{ Eliminating the Frame Pointer and the Arg Pointer */
+
+/* A C expression which is nonzero if a function must have and use a frame
+ pointer. This expression is evaluated in the reload pass. If its value is
+ nonzero the function will have a frame pointer.
+
+ The expression can in principle examine the current function and decide
+ according to the facts, but on most machines the constant 0 or the constant
+ 1 suffices. Use 0 when the machine allows code to be generated with no
+ frame pointer, and doing so saves some time or space. Use 1 when there is
+ no possible advantage to avoiding a frame pointer.
+
+ In certain cases, the compiler does not know how to produce valid code
+ without a frame pointer. The compiler recognizes those cases and
+ automatically gives the function a frame pointer regardless of what
+ `FRAME_POINTER_REQUIRED' says. You don't need to worry about them.
+
+ In a function that does not require a frame pointer, the frame pointer
+ register can be allocated for ordinary usage, unless you mark it as a fixed
+ register. See `FIXED_REGISTERS' for more information. */
+/* #define FRAME_POINTER_REQUIRED 0 */
+#define FRAME_POINTER_REQUIRED \
+ (flag_omit_frame_pointer == 0 || current_function_pretend_args_size > 0)
+
+/* A C statement to store in the variable DEPTH_VAR the difference between the
+ frame pointer and the stack pointer values immediately after the function
+ prologue. The value would be computed from information such as the result
+ of `get_frame_size ()' and the tables of registers `regs_ever_live' and
+ `call_used_regs'.
+
+ If `ELIMINABLE_REGS' is defined, this macro will be not be used and need not
+ be defined. Otherwise, it must be defined even if `FRAME_POINTER_REQUIRED'
+ is defined to always be true; in that case, you may set DEPTH-VAR to
+ anything. */
+/* #define INITIAL_FRAME_POINTER_OFFSET(DEPTH_VAR) */
+
+/* If defined, this macro specifies a table of register pairs used to eliminate
+ unneeded registers that point into the stack frame. If it is not defined,
+ the only elimination attempted by the compiler is to replace references to
+ the frame pointer with references to the stack pointer.
+
+ The definition of this macro is a list of structure initializations, each of
+ which specifies an original and replacement register.
+
+ On some machines, the position of the argument pointer is not known until
+ the compilation is completed. In such a case, a separate hard register must
+ be used for the argument pointer. This register can be eliminated by
+ replacing it with either the frame pointer or the argument pointer,
+ depending on whether or not the frame pointer has been eliminated.
+
+ In this case, you might specify:
+ #define ELIMINABLE_REGS \
+ {{ARG_POINTER_REGNUM, STACK_POINTER_REGNUM}, \
+ {ARG_POINTER_REGNUM, FRAME_POINTER_REGNUM}, \
+ {FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM}}
+
+ Note that the elimination of the argument pointer with the stack pointer is
+ specified first since that is the preferred elimination. */
+
+#define ELIMINABLE_REGS \
+{ \
+ {ARG_POINTER_REGNUM, STACK_POINTER_REGNUM}, \
+ {ARG_POINTER_REGNUM, FRAME_POINTER_REGNUM}, \
+ {FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM} \
+}
+
+/* A C expression that returns non-zero if the compiler is allowed to try to
+ replace register number FROM with register number TO. This macro
+ need only be defined if `ELIMINABLE_REGS' is defined, and will usually be
+ the constant 1, since most of the cases preventing register elimination are
+ things that the compiler already knows about. */
+
+#define CAN_ELIMINATE(FROM, TO) \
+ ((TO) == FRAME_POINTER_REGNUM || ! frame_pointer_needed)
+
+/* This macro is similar to `INITIAL_FRAME_POINTER_OFFSET'. It specifies the
+ initial difference between the specified pair of registers. This macro must
+ be defined if `ELIMINABLE_REGS' is defined. */
+#define INITIAL_ELIMINATION_OFFSET(FROM, TO, OFFSET) \
+ (OFFSET) = fr30_compute_frame_size (FROM, TO)
+
+/* Define this macro if the `longjmp' function restores registers from the
+ stack frames, rather than from those saved specifically by `setjmp'.
+ Certain quantities must not be kept in registers across a call to `setjmp'
+ on such machines. */
+/* #define LONGJMP_RESTORE_FROM_STACK */
+
+/*}}}*/ \f
+/*{{{ Passing Function Arguments on the Stack */
+
+/* Define this macro if an argument declared in a prototype as an integral type
+ smaller than `int' should actually be passed as an `int'. In addition to
+ avoiding errors in certain cases of mismatch, it also makes for better code
+ on certain machines. */
+#define PROMOTE_PROTOTYPES 1
+
+/* A C expression that is the number of bytes actually pushed onto the stack
+ when an instruction attempts to push NPUSHED bytes.
+
+ If the target machine does not have a push instruction, do not define this
+ macro. That directs GNU CC to use an alternate strategy: to allocate the
+ entire argument block and then store the arguments into it.
+
+ On some machines, the definition
+
+ #define PUSH_ROUNDING(BYTES) (BYTES)
+
+ will suffice. But on other machines, instructions that appear to push one
+ byte actually push two bytes in an attempt to maintain alignment. Then the
+ definition should be
+
+ #define PUSH_ROUNDING(BYTES) (((BYTES) + 1) & ~1) */
+/* #define PUSH_ROUNDING(NPUSHED) */
+
+/* If defined, the maximum amount of space required for outgoing arguments will
+ be computed and placed into the variable
+ `current_function_outgoing_args_size'. No space will be pushed onto the
+ stack for each call; instead, the function prologue should increase the
+ stack frame size by this amount.
+
+ Defining both `PUSH_ROUNDING' and `ACCUMULATE_OUTGOING_ARGS' is not
+ proper. */
+#define ACCUMULATE_OUTGOING_ARGS
+
+/* Define this macro if functions should assume that stack space has been
+ allocated for arguments even when their values are passed in registers.
+
+ The value of this macro is the size, in bytes, of the area reserved for
+ arguments passed in registers for the function represented by FNDECL.
+
+ This space can be allocated by the caller, or be a part of the
+ machine-dependent stack frame: `OUTGOING_REG_PARM_STACK_SPACE' says
+ which. */
+/* #define REG_PARM_STACK_SPACE(FNDECL) */
+
+/* Define these macros in addition to the one above if functions might allocate
+ stack space for arguments even when their values are passed in registers.
+ These should be used when the stack space allocated for arguments in
+ registers is not a simple constant independent of the function declaration.
+
+ The value of the first macro is the size, in bytes, of the area that we
+ should initially assume would be reserved for arguments passed in registers.
+
+ The value of the second macro is the actual size, in bytes, of the area that
+ will be reserved for arguments passed in registers. This takes two
+ arguments: an integer representing the number of bytes of fixed sized
+ arguments on the stack, and a tree representing the number of bytes of
+ variable sized arguments on the stack.
+
+ When these macros are defined, `REG_PARM_STACK_SPACE' will only be called
+ for libcall functions, the current function, or for a function being called
+ when it is known that such stack space must be allocated. In each case this
+ value can be easily computed.
+
+ When deciding whether a called function needs such stack space, and how much
+ space to reserve, GNU CC uses these two macros instead of
+ `REG_PARM_STACK_SPACE'. */
+/* #define MAYBE_REG_PARM_STACK_SPACE */
+/* #define FINAL_REG_PARM_STACK_SPACE(CONST_SIZE, VAR_SIZE) */
+
+/* Define this if it is the responsibility of the caller to allocate the area
+ reserved for arguments passed in registers.
+
+ If `ACCUMULATE_OUTGOING_ARGS' is defined, this macro controls whether the
+ space for these arguments counts in the value of
+ `current_function_outgoing_args_size'. */
+/* #define OUTGOING_REG_PARM_STACK_SPACE */
+
+/* Define this macro if `REG_PARM_STACK_SPACE' is defined, but the stack
+ parameters don't skip the area specified by it.
+
+ Normally, when a parameter is not passed in registers, it is placed on the
+ stack beyond the `REG_PARM_STACK_SPACE' area. Defining this macro
+ suppresses this behavior and causes the parameter to be passed on the stack
+ in its natural location. */
+/* #define STACK_PARMS_IN_REG_PARM_AREA */
+
+/* A C expression that should indicate the number of bytes of its own arguments
+ that a function pops on returning, or 0 if the function pops no arguments
+ and the caller must therefore pop them all after the function returns.
+
+ FUNDECL is a C variable whose value is a tree node that describes the
+ function in question. Normally it is a node of type `FUNCTION_DECL' that
+ describes the declaration of the function. From this it is possible to
+ obtain the DECL_MACHINE_ATTRIBUTES of the function.
+
+ FUNTYPE is a C variable whose value is a tree node that describes the
+ function in question. Normally it is a node of type `FUNCTION_TYPE' that
+ describes the data type of the function. From this it is possible to obtain
+ the data types of the value and arguments (if known).
+
+ When a call to a library function is being considered, FUNTYPE will contain
+ an identifier node for the library function. Thus, if you need to
+ distinguish among various library functions, you can do so by their names.
+ Note that "library function" in this context means a function used to
+ perform arithmetic, whose name is known specially in the compiler and was
+ not mentioned in the C code being compiled.
+
+ STACK-SIZE is the number of bytes of arguments passed on the stack. If a
+ variable number of bytes is passed, it is zero, and argument popping will
+ always be the responsibility of the calling function.
+
+ On the Vax, all functions always pop their arguments, so the definition of
+ this macro is STACK-SIZE. On the 68000, using the standard calling
+ convention, no functions pop their arguments, so the value of the macro is
+ always 0 in this case. But an alternative calling convention is available
+ in which functions that take a fixed number of arguments pop them but other
+ functions (such as `printf') pop nothing (the caller pops all). When this
+ convention is in use, FUNTYPE is examined to determine whether a function
+ takes a fixed number of arguments. */
+#define RETURN_POPS_ARGS(FUNDECL, FUNTYPE, STACK_SIZE) 0
+
+/* Implement `va_arg'. */
+#define EXPAND_BUILTIN_VA_ARG(valist, type) \
+ fr30_va_arg (valist, type)
+
+/*}}}*/ \f
+/*{{{ Function Arguments in Registers */
+
+/* Nonzero if we do not know how to pass TYPE solely in registers.
+ We cannot do so in the following cases:
+
+ - if the type has variable size
+ - if the type is marked as addressable (it is required to be constructed
+ into the stack)
+ - if the type is a structure or union. */
+
+#define MUST_PASS_IN_STACK(MODE,TYPE) \
+ (((MODE) == BLKmode) \
+ || ((TYPE) != 0 \
+ && (TREE_CODE (TYPE_SIZE (TYPE)) != INTEGER_CST \
+ || TREE_CODE (TYPE) == RECORD_TYPE \
+ || TREE_CODE (TYPE) == UNION_TYPE \
+ || TREE_CODE (TYPE) == QUAL_UNION_TYPE \
+ || TREE_ADDRESSABLE (TYPE))))
+
+/* The number of register assigned to holding function arguments. */
+
+#define FR30_NUM_ARG_REGS 4
+
+/* A C expression that controls whether a function argument is passed in a
+ register, and which register.
+
+ The usual way to make the ANSI library `stdarg.h' work on a machine where
+ some arguments are usually passed in registers, is to cause nameless
+ arguments to be passed on the stack instead. This is done by making
+ `FUNCTION_ARG' return 0 whenever NAMED is 0.
+
+ You may use the macro `MUST_PASS_IN_STACK (MODE, TYPE)' in the definition of
+ this macro to determine if this argument is of a type that must be passed in
+ the stack. If `REG_PARM_STACK_SPACE' is not defined and `FUNCTION_ARG'
+ returns non-zero for such an argument, the compiler will abort. If
+ `REG_PARM_STACK_SPACE' is defined, the argument will be computed in the
+ stack and then loaded into a register. */
+
+#define FUNCTION_ARG(CUM, MODE, TYPE, NAMED) \
+ ( (NAMED) == 0 ? NULL_RTX \
+ : MUST_PASS_IN_STACK (MODE, TYPE) ? NULL_RTX \
+ : (CUM) >= FR30_NUM_ARG_REGS ? NULL_RTX \
+ : gen_rtx (REG, MODE, CUM + FIRST_ARG_REGNUM))
+
+/* A C type for declaring a variable that is used as the first argument of
+ `FUNCTION_ARG' and other related values. For some target machines, the type
+ `int' suffices and can hold the number of bytes of argument so far.
+
+ There is no need to record in `CUMULATIVE_ARGS' anything about the arguments
+ that have been passed on the stack. The compiler has other variables to
+ keep track of that. For target machines on which all arguments are passed
+ on the stack, there is no need to store anything in `CUMULATIVE_ARGS';
+ however, the data structure must exist and should not be empty, so use
+ `int'. */
+/* On the FR30 this value is an accumulating count of the number of argument
+ registers that have been filled with argument values, as opposed to say,
+ the number of bytes of argument accumulated so far. */
+typedef int CUMULATIVE_ARGS;
+
+/* A C expression for the number of words, at the beginning of an argument,
+ must be put in registers. The value must be zero for arguments that are
+ passed entirely in registers or that are entirely pushed on the stack.
+
+ On some machines, certain arguments must be passed partially in registers
+ and partially in memory. On these machines, typically the first N words of
+ arguments are passed in registers, and the rest on the stack. If a
+ multi-word argument (a `double' or a structure) crosses that boundary, its
+ first few words must be passed in registers and the rest must be pushed.
+ This macro tells the compiler when this occurs, and how many of the words
+ should go in registers.
+
+ `FUNCTION_ARG' for these arguments should return the first register to be
+ used by the caller for this argument; likewise `FUNCTION_INCOMING_ARG', for
+ the called function. */
+#define FUNCTION_ARG_PARTIAL_NREGS(CUM, MODE, TYPE, NAMED) \
+ fr30_function_arg_partial_nregs (CUM, MODE, TYPE, NAMED)
+
+extern int fr30_function_arg_partial_nregs PROTO ((CUMULATIVE_ARGS, int, Tree, int));
+
+/* A C expression that indicates when an argument must be passed by reference.
+ If nonzero for an argument, a copy of that argument is made in memory and a
+ pointer to the argument is passed instead of the argument itself. The
+ pointer is passed in whatever way is appropriate for passing a pointer to
+ that type.
+
+ On machines where `REG_PARM_STACK_SPACE' is not defined, a suitable
+ definition of this macro might be:
+ #define FUNCTION_ARG_PASS_BY_REFERENCE(CUM, MODE, TYPE, NAMED) \
+ MUST_PASS_IN_STACK (MODE, TYPE) */
+#define FUNCTION_ARG_PASS_BY_REFERENCE(CUM, MODE, TYPE, NAMED) \
+ MUST_PASS_IN_STACK (MODE, TYPE)
+
+/* If defined, a C expression that indicates when it is more
+ desirable to keep an argument passed by invisible reference as a
+ reference, rather than copying it to a pseudo register. */
+/* #define FUNCTION_ARG_KEEP_AS_REFERENCE(CUM, MODE, TYPE, NAMED) */
+
+/* If defined, a C expression that indicates when it is the called function's
+ responsibility to make a copy of arguments passed by invisible reference.
+ Normally, the caller makes a copy and passes the address of the copy to the
+ routine being called. When FUNCTION_ARG_CALLEE_COPIES is defined and is
+ nonzero, the caller does not make a copy. Instead, it passes a pointer to
+ the "live" value. The called function must not modify this value. If it
+ can be determined that the value won't be modified, it need not make a copy;
+ otherwise a copy must be made. */
+/* #define FUNCTION_ARG_CALLEE_COPIES(CUM, MODE, TYPE, NAMED) */
+
+/* If defined, a C expression that indicates when it is more desirable to keep
+ an argument passed by invisible reference as a reference, rather than
+ copying it to a pseudo register. */
+/* #define FUNCTION_ARG_KEEP_AS_REFERENCE(CUM, MODE, TYPE, NAMED) */
+
+/* A C statement (sans semicolon) for initializing the variable CUM for the
+ state at the beginning of the argument list. The variable has type
+ `CUMULATIVE_ARGS'. The value of FNTYPE is the tree node for the data type
+ of the function which will receive the args, or 0 if the args are to a
+ compiler support library function. The value of INDIRECT is nonzero when
+ processing an indirect call, for example a call through a function pointer.
+ The value of INDIRECT is zero for a call to an explicitly named function, a
+ library function call, or when `INIT_CUMULATIVE_ARGS' is used to find
+ arguments for the function being compiled.
+
+ When processing a call to a compiler support library function, LIBNAME
+ identifies which one. It is a `symbol_ref' rtx which contains the name of
+ the function, as a string. LIBNAME is 0 when an ordinary C function call is
+ being processed. Thus, each time this macro is called, either LIBNAME or
+ FNTYPE is nonzero, but never both of them at once. */
+#define INIT_CUMULATIVE_ARGS(CUM, FNTYPE, LIBNAME, INDIRECT) (CUM) = 0
+
+/* Like `INIT_CUMULATIVE_ARGS' but overrides it for the purposes of finding the
+ arguments for the function being compiled. If this macro is undefined,
+ `INIT_CUMULATIVE_ARGS' is used instead.
+
+ The value passed for LIBNAME is always 0, since library routines with
+ special calling conventions are never compiled with GNU CC. The argument
+ LIBNAME exists for symmetry with `INIT_CUMULATIVE_ARGS'. */
+/* #define INIT_CUMULATIVE_INCOMING_ARGS(CUM, FNTYPE, LIBNAME) */
+
+/* A C statement (sans semicolon) to update the summarizer variable CUM to
+ advance past an argument in the argument list. The values MODE, TYPE and
+ NAMED describe that argument. Once this is done, the variable CUM is
+ suitable for analyzing the *following* argument with `FUNCTION_ARG', etc.
+
+ This macro need not do anything if the argument in question was passed on
+ the stack. The compiler knows how to track the amount of stack space used
+ for arguments without any special help. */
+#define FUNCTION_ARG_ADVANCE(CUM, MODE, TYPE, NAMED) \
+ (CUM) += (NAMED) * fr30_num_arg_regs (MODE, TYPE)
+
+extern int fr30_num_arg_regs PROTO ((int, Tree));
+
+/* If defined, a C expression which determines whether, and in which direction,
+ to pad out an argument with extra space. The value should be of type `enum
+ direction': either `upward' to pad above the argument, `downward' to pad
+ below, or `none' to inhibit padding.
+
+ The *amount* of padding is always just enough to reach the next multiple of
+ `FUNCTION_ARG_BOUNDARY'; this macro does not control it.
+
+ This macro has a default definition which is right for most systems. For
+ little-endian machines, the default is to pad upward. For big-endian
+ machines, the default is to pad downward for an argument of constant size
+ shorter than an `int', and upward otherwise. */
+/* #define FUNCTION_ARG_PADDING(MODE, TYPE) */
+
+/* If defined, a C expression that gives the alignment boundary, in bits, of an
+ argument with the specified mode and type. If it is not defined,
+ `PARM_BOUNDARY' is used for all arguments. */
+/* #define FUNCTION_ARG_BOUNDARY(MODE, TYPE) */
+
+/* A C expression that is nonzero if REGNO is the number of a hard register in
+ which function arguments are sometimes passed. This does *not* include
+ implicit arguments such as the static chain and the structure-value address.
+ On many machines, no registers can be used for this purpose since all
+ function arguments are pushed on the stack. */
+#define FUNCTION_ARG_REGNO_P(REGNO) \
+ ((REGNO) >= FIRST_ARG_REGNUM && ((REGNO) < FIRST_ARG_REGNUM + FR30_NUM_ARG_REGS))
+
+/*}}}*/ \f
+/*{{{ How Scalar Function Values are Returned */
+
+/* Define this macro if `-traditional' should not cause functions declared to
+ return `float' to convert the value to `double'. */
+/* #define TRADITIONAL_RETURN_FLOAT */
+
+/* A C expression to create an RTX representing the place where a function
+ returns a value of data type VALTYPE. VALTYPE is a tree node representing a
+ data type. Write `TYPE_MODE (VALTYPE)' to get the machine mode used to
+ represent that type. On many machines, only the mode is relevant.
+ (Actually, on most machines, scalar values are returned in the same place
+ regardless of mode).
+
+ If `PROMOTE_FUNCTION_RETURN' is defined, you must apply the same promotion
+ rules specified in `PROMOTE_MODE' if VALTYPE is a scalar type.
+
+ If the precise function being called is known, FUNC is a tree node
+ (`FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This makes it
+ possible to use a different value-returning convention for specific
+ functions when all their calls are known.
+
+ `FUNCTION_VALUE' is not used for return vales with aggregate data types,
+ because these are returned in another way. See `STRUCT_VALUE_REGNUM' and
+ related macros, below. */
+#define FUNCTION_VALUE(VALTYPE, FUNC) \
+ gen_rtx_REG (TYPE_MODE (VALTYPE), RETURN_VALUE_REGNUM)
+
+/* A C expression to create an RTX representing the place where a library
+ function returns a value of mode MODE. If the precise function being called
+ is known, FUNC is a tree node (`FUNCTION_DECL') for it; otherwise, FUNC is a
+ null pointer. This makes it possible to use a different value-returning
+ convention for specific functions when all their calls are known.
+
+ Note that "library function" in this context means a compiler support
+ routine, used to perform arithmetic, whose name is known specially by the
+ compiler and was not mentioned in the C code being compiled.
+
+ The definition of `LIBRARY_VALUE' need not be concerned aggregate data
+ types, because none of the library functions returns such types. */
+#define LIBCALL_VALUE(MODE) gen_rtx (REG, MODE, RETURN_VALUE_REGNUM)
+
+/* A C expression that is nonzero if REGNO is the number of a hard register in
+ which the values of called function may come back. */
+
+#define FUNCTION_VALUE_REGNO_P(REGNO) ((REGNO) == RETURN_VALUE_REGNUM)
+
+/* Define this macro if `untyped_call' and `untyped_return' need more space
+ than is implied by `FUNCTION_VALUE_REGNO_P' for saving and restoring an
+ arbitrary return value. */
+/* #define APPLY_RESULT_SIZE */
+
+/*}}}*/ \f
+/*{{{ How Large Values are Returned */
+
+/* A C expression which can inhibit the returning of certain function values in
+ registers, based on the type of value. A nonzero value says to return the
+ function value in memory, just as large structures are always returned.
+ Here TYPE will be a C expression of type `tree', representing the data type
+ of the value.
+
+ Note that values of mode `BLKmode' must be explicitly handled by this macro.
+ Also, the option `-fpcc-struct-return' takes effect regardless of this
+ macro. On most systems, it is possible to leave the macro undefined; this
+ causes a default definition to be used, whose value is the constant 1 for
+ `BLKmode' values, and 0 otherwise.
+
+ Do not use this macro to indicate that structures and unions should always
+ be returned in memory. You should instead use `DEFAULT_PCC_STRUCT_RETURN'
+ to indicate this. */
+/* #define RETURN_IN_MEMORY(TYPE) */
+
+/* Define this macro to be 1 if all structure and union return values must be
+ in memory. Since this results in slower code, this should be defined only
+ if needed for compatibility with other compilers or with an ABI. If you
+ define this macro to be 0, then the conventions used for structure and union
+ return values are decided by the `RETURN_IN_MEMORY' macro.
+
+ If not defined, this defaults to the value 1. */
+#define DEFAULT_PCC_STRUCT_RETURN 1
+
+/* If the structure value address is passed in a register, then
+ `STRUCT_VALUE_REGNUM' should be the number of that register. */
+/* #define STRUCT_VALUE_REGNUM */
+
+/* If the structure value address is not passed in a register, define
+ `STRUCT_VALUE' as an expression returning an RTX for the place where the
+ address is passed. If it returns 0, the address is passed as an "invisible"
+ first argument. */
+#define STRUCT_VALUE 0
+
+/* On some architectures the place where the structure value address is found
+ by the called function is not the same place that the caller put it. This
+ can be due to register windows, or it could be because the function prologue
+ moves it to a different place.
+
+ If the incoming location of the structure value address is in a register,
+ define this macro as the register number. */
+/* #define STRUCT_VALUE_INCOMING_REGNUM */
+
+/* If the incoming location is not a register, then you should define
+ `STRUCT_VALUE_INCOMING' as an expression for an RTX for where the called
+ function should find the value. If it should find the value on the stack,
+ define this to create a `mem' which refers to the frame pointer. A
+ definition of 0 means that the address is passed as an "invisible" first
+ argument. */
+/* #define STRUCT_VALUE_INCOMING */
+
+/* Define this macro if the usual system convention on the target machine for
+ returning structures and unions is for the called function to return the
+ address of a static variable containing the value.
+
+ Do not define this if the usual system convention is for the caller to pass
+ an address to the subroutine.
+
+ This macro has effect in `-fpcc-struct-return' mode, but it does nothing
+ when you use `-freg-struct-return' mode. */
+/* #define PCC_STATIC_STRUCT_RETURN */
+
+/*}}}*/ \f
+/*{{{ Caller-Saves Register Allocation */
+
+/* Define this macro if function calls on the target machine do not preserve
+ any registers; in other words, if `CALL_USED_REGISTERS' has 1 for all
+ registers. This macro enables `-fcaller-saves' by default. Eventually that
+ option will be enabled by default on all machines and both the option and
+ this macro will be eliminated. */
+/* #define DEFAULT_CALLER_SAVES */
+
+/* A C expression to determine whether it is worthwhile to consider placing a
+ pseudo-register in a call-clobbered hard register and saving and restoring
+ it around each function call. The expression should be 1 when this is worth
+ doing, and 0 otherwise.
+
+ If you don't define this macro, a default is used which is good on most
+ machines: `4 * CALLS < REFS'. */
+/* #define CALLER_SAVE_PROFITABLE(REFS, CALLS) */
+
+/*}}}*/ \f
+/*{{{ Function Entry and Exit */
+
+/* A C compound statement that outputs the assembler code for entry to a
+ function. The prologue is responsible for setting up the stack frame,
+ initializing the frame pointer register, saving registers that must be
+ saved, and allocating SIZE additional bytes of storage for the local
+ variables. SIZE is an integer. FILE is a stdio stream to which the
+ assembler code should be output.
+
+ The label for the beginning of the function need not be output by this
+ macro. That has already been done when the macro is run.
+
+ To determine which registers to save, the macro can refer to the array
+ `regs_ever_live': element R is nonzero if hard register R is used anywhere
+ within the function. This implies the function prologue should save
+ register R, provided it is not one of the call-used registers.
+ (`FUNCTION_EPILOGUE' must likewise use `regs_ever_live'.)
+
+ On machines that have "register windows", the function entry code does not
+ save on the stack the registers that are in the windows, even if they are
+ supposed to be preserved by function calls; instead it takes appropriate
+ steps to "push" the register stack, if any non-call-used registers are used
+ in the function.
+
+ On machines where functions may or may not have frame-pointers, the function
+ entry code must vary accordingly; it must set up the frame pointer if one is
+ wanted, and not otherwise. To determine whether a frame pointer is in
+ wanted, the macro can refer to the variable `frame_pointer_needed'. The
+ variable's value will be 1 at run time in a function that needs a frame
+ pointer. *Note Elimination::.
+
+ The function entry code is responsible for allocating any stack space
+ required for the function. This stack space consists of the regions listed
+ below. In most cases, these regions are allocated in the order listed, with
+ the last listed region closest to the top of the stack (the lowest address
+ if `STACK_GROWS_DOWNWARD' is defined, and the highest address if it is not
+ defined). You can use a different order for a machine if doing so is more
+ convenient or required for compatibility reasons. Except in cases where
+ required by standard or by a debugger, there is no reason why the stack
+ layout used by GCC need agree with that used by other compilers for a
+ machine.
+
+ * A region of `current_function_pretend_args_size' bytes of
+ uninitialized space just underneath the first argument
+ arriving on the stack. (This may not be at the very start of
+ the allocated stack region if the calling sequence has pushed
+ anything else since pushing the stack arguments. But
+ usually, on such machines, nothing else has been pushed yet,
+ because the function prologue itself does all the pushing.)
+ This region is used on machines where an argument may be
+ passed partly in registers and partly in memory, and, in some
+ cases to support the features in `varargs.h' and `stdargs.h'.
+
+ * An area of memory used to save certain registers used by the
+ function. The size of this area, which may also include
+ space for such things as the return address and pointers to
+ previous stack frames, is machine-specific and usually
+ depends on which registers have been used in the function.
+ Machines with register windows often do not require a save
+ area.
+
+ * A region of at least SIZE bytes, possibly rounded up to an
+ allocation boundary, to contain the local variables of the
+ function. On some machines, this region and the save area
+ may occur in the opposite order, with the save area closer to
+ the top of the stack.
+
+ * Optionally, when `ACCUMULATE_OUTGOING_ARGS' is defined, a
+ region of `current_function_outgoing_args_size' bytes to be
+ used for outgoing argument lists of the function.
+
+ Normally, it is necessary for the macros `FUNCTION_PROLOGUE' and
+ `FUNCTION_EPILOGUE' to treat leaf functions specially. The C variable
+ `leaf_function' is nonzero for such a function. */
+/* #define FUNCTION_PROLOGUE(FILE, SIZE) */
+
+/* Define this macro as a C expression that is nonzero if the return
+ instruction or the function epilogue ignores the value of the stack pointer;
+ in other words, if it is safe to delete an instruction to adjust the stack
+ pointer before a return from the function.
+
+ Note that this macro's value is relevant only for functions for which frame
+ pointers are maintained. It is never safe to delete a final stack
+ adjustment in a function that has no frame pointer, and the compiler knows
+ this regardless of `EXIT_IGNORE_STACK'. */
+/* #define EXIT_IGNORE_STACK */
+
+/* Define this macro as a C expression that is nonzero for registers
+ are used by the epilogue or the `return' pattern. The stack and
+ frame pointer registers are already be assumed to be used as
+ needed. */
+/* #define EPILOGUE_USES(REGNO) */
+
+/* A C compound statement that outputs the assembler code for exit from a
+ function. The epilogue is responsible for restoring the saved registers and
+ stack pointer to their values when the function was called, and returning
+ control to the caller. This macro takes the same arguments as the macro
+ `FUNCTION_PROLOGUE', and the registers to restore are determined from
+ `regs_ever_live' and `CALL_USED_REGISTERS' in the same way.
+
+ On some machines, there is a single instruction that does all the work of
+ returning from the function. On these machines, give that instruction the
+ name `return' and do not define the macro `FUNCTION_EPILOGUE' at all.
+
+ Do not define a pattern named `return' if you want the `FUNCTION_EPILOGUE'
+ to be used. If you want the target switches to control whether return
+ instructions or epilogues are used, define a `return' pattern with a
+ validity condition that tests the target switches appropriately. If the
+ `return' pattern's validity condition is false, epilogues will be used.
+
+ On machines where functions may or may not have frame-pointers, the function
+ exit code must vary accordingly. Sometimes the code for these two cases is
+ completely different. To determine whether a frame pointer is wanted, the
+ macro can refer to the variable `frame_pointer_needed'. The variable's
+ value will be 1 when compiling a function that needs a frame pointer.
+
+ Normally, `FUNCTION_PROLOGUE' and `FUNCTION_EPILOGUE' must treat leaf
+ functions specially. The C variable `leaf_function' is nonzero for such a
+ function.
+
+ On some machines, some functions pop their arguments on exit while others
+ leave that for the caller to do. For example, the 68020 when given `-mrtd'
+ pops arguments in functions that take a fixed number of arguments.
+
+ Your definition of the macro `RETURN_POPS_ARGS' decides which functions pop
+ their own arguments. `FUNCTION_EPILOGUE' needs to know what was decided.
+ The variable that is called `current_function_pops_args' is the number of
+ bytes of its arguments that a function should pop. *Note Scalar Return::. */
+/* #define FUNCTION_EPILOGUE(FILE, SIZE) */
+
+/* Define this macro if the function epilogue contains delay slots to which
+ instructions from the rest of the function can be "moved". The definition
+ should be a C expression whose value is an integer representing the number
+ of delay slots there. */
+/* #define DELAY_SLOTS_FOR_EPILOGUE */
+
+/* A C expression that returns 1 if INSN can be placed in delay slot number N
+ of the epilogue.
+
+ The argument N is an integer which identifies the delay slot now being
+ considered (since different slots may have different rules of eligibility).
+ It is never negative and is always less than the number of epilogue delay
+ slots (what `DELAY_SLOTS_FOR_EPILOGUE' returns). If you reject a particular
+ insn for a given delay slot, in principle, it may be reconsidered for a
+ subsequent delay slot. Also, other insns may (at least in principle) be
+ considered for the so far unfilled delay slot.
+
+ The insns accepted to fill the epilogue delay slots are put in an
+ RTL list made with `insn_list' objects, stored in the variable
+ `current_function_epilogue_delay_list'. The insn for the first
+ delay slot comes first in the list. Your definition of the macro
+ `FUNCTION_EPILOGUE' should fill the delay slots by outputting the
+ insns in this list, usually by calling `final_scan_insn'.
+
+ You need not define this macro if you did not define
+ `DELAY_SLOTS_FOR_EPILOGUE'. */
+/* #define ELIGIBLE_FOR_EPILOGUE_DELAY(INSN, N) */
+
+/* A C compound statement that outputs the assembler code for a thunk function,
+ used to implement C++ virtual function calls with multiple inheritance. The
+ thunk acts as a wrapper around a virtual function, adjusting the implicit
+ object parameter before handing control off to the real function.
+
+ First, emit code to add the integer DELTA to the location that contains the
+ incoming first argument. Assume that this argument contains a pointer, and
+ is the one used to pass the `this' pointer in C++. This is the incoming
+ argument *before* the function prologue, e.g. `%o0' on a sparc. The
+ addition must preserve the values of all other incoming arguments.
+
+ After the addition, emit code to jump to FUNCTION, which is a
+ `FUNCTION_DECL'. This is a direct pure jump, not a call, and does not touch
+ the return address. Hence returning from FUNCTION will return to whoever
+ called the current `thunk'.
+
+ The effect must be as if FUNCTION had been called directly with the adjusted
+ first argument. This macro is responsible for emitting all of the code for
+ a thunk function; `FUNCTION_PROLOGUE' and `FUNCTION_EPILOGUE' are not
+ invoked.
+
+ The THUNK_FNDECL is redundant. (DELTA and FUNCTION have already been
+ extracted from it.) It might possibly be useful on some targets, but
+ probably not.
+
+ If you do not define this macro, the target-independent code in the C++
+ frontend will generate a less efficient heavyweight thunk that calls
+ FUNCTION instead of jumping to it. The generic approach does not support
+ varargs. */
+/* #define ASM_OUTPUT_MI_THUNK(FILE, THUNK_FNDECL, DELTA, FUNCTION) */
+
+/*}}}*/ \f
+/*{{{ Generating Code for Profiling. */
+
+/* A C statement or compound statement to output to FILE some assembler code to
+ call the profiling subroutine `mcount'. Before calling, the assembler code
+ must load the address of a counter variable into a register where `mcount'
+ expects to find the address. The name of this variable is `LP' followed by
+ the number LABELNO, so you would generate the name using `LP%d' in a
+ `fprintf'.
+
+ The details of how the address should be passed to `mcount' are determined
+ by your operating system environment, not by GNU CC. To figure them out,
+ compile a small program for profiling using the system's installed C
+ compiler and look at the assembler code that results. */
+#define FUNCTION_PROFILER(FILE, LABELNO) \
+{ \
+ fprintf (FILE, "\t mov rp, r1\n" ); \
+ fprintf (FILE, "\t ldi:32 mcount, r0\n" ); \
+ fprintf (FILE, "\t call @r0\n" ); \
+ fprintf (FILE, ".word\tLP%d\n", LABELNO); \
+}
+
+/* Define this macro if the code for function profiling should come before the
+ function prologue. Normally, the profiling code comes after. */
+/* #define PROFILE_BEFORE_PROLOGUE */
+
+/* A C statement or compound statement to output to FILE some assembler code to
+ initialize basic-block profiling for the current object module. The global
+ compile flag `profile_block_flag' distingishes two profile modes.
+
+ profile_block_flag != 2'
+ Output code to call the subroutine `__bb_init_func' once per
+ object module, passing it as its sole argument the address of
+ a block allocated in the object module.
+
+ The name of the block is a local symbol made with this
+ statement:
+
+ ASM_GENERATE_INTERNAL_LABEL (BUFFER, "LPBX", 0);
+
+ Of course, since you are writing the definition of
+ `ASM_GENERATE_INTERNAL_LABEL' as well as that of this macro,
+ you can take a short cut in the definition of this macro and
+ use the name that you know will result.
+
+ The first word of this block is a flag which will be nonzero
+ if the object module has already been initialized. So test
+ this word first, and do not call `__bb_init_func' if the flag
+ is nonzero. BLOCK_OR_LABEL contains a unique number which
+ may be used to generate a label as a branch destination when
+ `__bb_init_func' will not be called.
+
+ Described in assembler language, the code to be output looks
+ like:
+
+ cmp (LPBX0),0
+ bne local_label
+ parameter1 <- LPBX0
+ call __bb_init_func
+ local_label:
+
+ profile_block_flag == 2'
+ Output code to call the subroutine `__bb_init_trace_func' and
+ pass two parameters to it. The first parameter is the same as
+ for `__bb_init_func'. The second parameter is the number of
+ the first basic block of the function as given by
+ BLOCK_OR_LABEL. Note that `__bb_init_trace_func' has to be
+ called, even if the object module has been initialized
+ already.
+
+ Described in assembler language, the code to be output looks
+ like:
+ parameter1 <- LPBX0
+ parameter2 <- BLOCK_OR_LABEL
+ call __bb_init_trace_func */
+/* #define FUNCTION_BLOCK_PROFILER (FILE, LABELNO) */
+
+/* A C statement or compound statement to output to FILE some assembler code to
+ increment the count associated with the basic block number BLOCKNO. The
+ global compile flag `profile_block_flag' distingishes two profile modes.
+
+ profile_block_flag != 2'
+ Output code to increment the counter directly. Basic blocks
+ are numbered separately from zero within each compilation.
+ The count associated with block number BLOCKNO is at index
+ BLOCKNO in a vector of words; the name of this array is a
+ local symbol made with this statement:
+
+ ASM_GENERATE_INTERNAL_LABEL (BUFFER, "LPBX", 2);
+
+ Of course, since you are writing the definition of
+ `ASM_GENERATE_INTERNAL_LABEL' as well as that of this macro,
+ you can take a short cut in the definition of this macro and
+ use the name that you know will result.
+
+ Described in assembler language, the code to be output looks
+ like:
+
+ inc (LPBX2+4*BLOCKNO)
+
+ profile_block_flag == 2'
+ Output code to initialize the global structure `__bb' and
+ call the function `__bb_trace_func', which will increment the
+ counter.
+
+ `__bb' consists of two words. In the first word, the current
+ basic block number, as given by BLOCKNO, has to be stored. In
+ the second word, the address of a block allocated in the
+ object module has to be stored. The address is given by the
+ label created with this statement:
+
+ ASM_GENERATE_INTERNAL_LABEL (BUFFER, "LPBX", 0);
+
+ Described in assembler language, the code to be output looks
+ like:
+ move BLOCKNO -> (__bb)
+ move LPBX0 -> (__bb+4)
+ call __bb_trace_func */
+/* #define BLOCK_PROFILER(FILE, BLOCKNO) */
+
+/* A C statement or compound statement to output to FILE assembler
+ code to call function `__bb_trace_ret'. The assembler code should
+ only be output if the global compile flag `profile_block_flag' ==
+ 2. This macro has to be used at every place where code for
+ returning from a function is generated (e.g. `FUNCTION_EPILOGUE').
+ Although you have to write the definition of `FUNCTION_EPILOGUE'
+ as well, you have to define this macro to tell the compiler, that
+ the proper call to `__bb_trace_ret' is produced. */
+/* #define FUNCTION_BLOCK_PROFILER_EXIT(FILE) */
+
+/* A C statement or compound statement to save all registers, which may be
+ clobbered by a function call, including condition codes. The `asm'
+ statement will be mostly likely needed to handle this task. Local labels in
+ the assembler code can be concatenated with the string ID, to obtain a
+ unique lable name.
+
+ Registers or condition codes clobbered by `FUNCTION_PROLOGUE' or
+ `FUNCTION_EPILOGUE' must be saved in the macros `FUNCTION_BLOCK_PROFILER',
+ `FUNCTION_BLOCK_PROFILER_EXIT' and `BLOCK_PROFILER' prior calling
+ `__bb_init_trace_func', `__bb_trace_ret' and `__bb_trace_func' respectively. */
+/* #define MACHINE_STATE_SAVE(ID) */
+
+/* A C statement or compound statement to restore all registers, including
+ condition codes, saved by `MACHINE_STATE_SAVE'.
+
+ Registers or condition codes clobbered by `FUNCTION_PROLOGUE' or
+ `FUNCTION_EPILOGUE' must be restored in the macros
+ `FUNCTION_BLOCK_PROFILER', `FUNCTION_BLOCK_PROFILER_EXIT' and
+ `BLOCK_PROFILER' after calling `__bb_init_trace_func', `__bb_trace_ret' and
+ `__bb_trace_func' respectively. */
+/* #define MACHINE_STATE_RESTORE(ID) */
+
+/* A C function or functions which are needed in the library to support block
+ profiling. */
+/* #define BLOCK_PROFILER_CODE */
+
+/*}}}*/ \f
+/*{{{ Implementing the VARARGS Macros. */
+
+/* If defined, is a C expression that produces the machine-specific code for a
+ call to `__builtin_saveregs'. This code will be moved to the very beginning
+ of the function, before any parameter access are made. The return value of
+ this function should be an RTX that contains the value to use as the return
+ of `__builtin_saveregs'.
+
+ The argument ARGS is a `tree_list' containing the arguments that were passed
+ to `__builtin_saveregs'.
+
+ If this macro is not defined, the compiler will output an ordinary call to
+ the library function `__builtin_saveregs'. */
+/* #define EXPAND_BUILTIN_SAVEREGS(ARGS) */
+
+/* This macro offers an alternative to using `__builtin_saveregs' and defining
+ the macro `EXPAND_BUILTIN_SAVEREGS'. Use it to store the anonymous register
+ arguments into the stack so that all the arguments appear to have been
+ passed consecutively on the stack. Once this is done, you can use the
+ standard implementation of varargs that works for machines that pass all
+ their arguments on the stack.
+
+ The argument ARGS_SO_FAR is the `CUMULATIVE_ARGS' data structure, containing
+ the values that obtain after processing of the named arguments. The
+ arguments MODE and TYPE describe the last named argument--its machine mode
+ and its data type as a tree node.
+
+ The macro implementation should do two things: first, push onto the stack
+ all the argument registers *not* used for the named arguments, and second,
+ store the size of the data thus pushed into the `int'-valued variable whose
+ name is supplied as the argument PRETEND_ARGS_SIZE. The value that you
+ store here will serve as additional offset for setting up the stack frame.
+
+ Because you must generate code to push the anonymous arguments at compile
+ time without knowing their data types, `SETUP_INCOMING_VARARGS' is only
+ useful on machines that have just a single category of argument register and
+ use it uniformly for all data types.
+
+ If the argument SECOND_TIME is nonzero, it means that the arguments of the
+ function are being analyzed for the second time. This happens for an inline
+ function, which is not actually compiled until the end of the source file.
+ The macro `SETUP_INCOMING_VARARGS' should not generate any instructions in
+ this case. */
+#define SETUP_INCOMING_VARARGS(ARGS_SO_FAR, MODE, TYPE, PRETEND_ARGS_SIZE, SECOND_TIME) \
+ if (! SECOND_TIME) \
+ fr30_setup_incoming_varargs (ARGS_SO_FAR, MODE, TYPE, & PRETEND_ARGS_SIZE)
+
+extern void fr30_setup_incoming_varargs
+ PROTO ((CUMULATIVE_ARGS, int, Tree, int *));
+
+/* Define this macro if the location where a function argument is passed
+ depends on whether or not it is a named argument.
+
+ This macro controls how the NAMED argument to `FUNCTION_ARG' is set for
+ varargs and stdarg functions. With this macro defined, the NAMED argument
+ is always true for named arguments, and false for unnamed arguments. If
+ this is not defined, but `SETUP_INCOMING_VARARGS' is defined, then all
+ arguments are treated as named. Otherwise, all named arguments except the
+ last are treated as named. */
+#define STRICT_ARGUMENT_NAMING 0
+
+/*}}}*/ \f
+/*{{{ Trampolines for Nested Functions. */
+
+/* On the FR30, the trampoline is:
+
+ ldi:32 STATIC, r12
+ ldi:32 FUNCTION, r0
+ jmp @r0 */
+
+/* A C statement to output, on the stream FILE, assembler code for a block of
+ data that contains the constant parts of a trampoline. This code should not
+ include a label--the label is taken care of automatically. */
+#define TRAMPOLINE_TEMPLATE(FILE) \
+{ \
+ fprintf (FILE, "\tldi:32\t#0, %s\n", reg_names [STATIC_CHAIN_REGNUM]); \
+ fprintf (FILE, "\tldi:32\t#0, %s\n", reg_names [COMPILER_SCRATCH_REGISTER]); \
+ fprintf (FILE, "\tjmp\t@%s\n", reg_names [COMPILER_SCRATCH_REGISTER]); \
+}
+
+/* The name of a subroutine to switch to the section in which the trampoline
+ template is to be placed. The default is a value of
+ `readonly_data_section', which places the trampoline in the section
+ containing read-only data. */
+/* #define TRAMPOLINE_SECTION */
+
+/* A C expression for the size in bytes of the trampoline, as an integer. */
+#define TRAMPOLINE_SIZE 14
+
+/* Alignment required for trampolines, in bits.
+
+ If you don't define this macro, the value of `BIGGEST_ALIGNMENT' is used for
+ aligning trampolines. */
+/* #define TRAMPOLINE_ALIGNMENT */
+
+/* A C statement to initialize the variable parts of a trampoline. ADDR is an
+ RTX for the address of the trampoline; FNADDR is an RTX for the address of
+ the nested function; STATIC_CHAIN is an RTX for the static chain value that
+ should be passed to the function when it is called. */
+#define INITIALIZE_TRAMPOLINE(ADDR, FNADDR, STATIC_CHAIN) \
+do \
+{ \
+ emit_move_insn (gen_rtx (MEM, SImode, plus_constant (ADDR, 2)), STATIC_CHAIN);\
+ emit_move_insn (gen_rtx (MEM, SImode, plus_constant (ADDR, 8)), FNADDR); \
+} while (0);
+
+/* A C expression to allocate run-time space for a trampoline. The expression
+ value should be an RTX representing a memory reference to the space for the
+ trampoline.
+
+ If this macro is not defined, by default the trampoline is allocated as a
+ stack slot. This default is right for most machines. The exceptions are
+ machines where it is impossible to execute instructions in the stack area.
+ On such machines, you may have to implement a separate stack, using this
+ macro in conjunction with `FUNCTION_PROLOGUE' and `FUNCTION_EPILOGUE'.
+
+ FP points to a data structure, a `struct function', which describes the
+ compilation status of the immediate containing function of the function
+ which the trampoline is for. Normally (when `ALLOCATE_TRAMPOLINE' is not
+ defined), the stack slot for the trampoline is in the stack frame of this
+ containing function. Other allocation strategies probably must do something
+ analogous with this information. */
+/* #define ALLOCATE_TRAMPOLINE(FP) */
+
+/* Implementing trampolines is difficult on many machines because they have
+ separate instruction and data caches. Writing into a stack location fails
+ to clear the memory in the instruction cache, so when the program jumps to
+ that location, it executes the old contents.
+
+ Here are two possible solutions. One is to clear the relevant parts of the
+ instruction cache whenever a trampoline is set up. The other is to make all
+ trampolines identical, by having them jump to a standard subroutine. The
+ former technique makes trampoline execution faster; the latter makes
+ initialization faster.
+
+ To clear the instruction cache when a trampoline is initialized, define the
+ following macros which describe the shape of the cache. */
+
+/* The total size in bytes of the cache. */
+/* #define INSN_CACHE_SIZE */
+
+/* The length in bytes of each cache line. The cache is divided into cache
+ lines which are disjoint slots, each holding a contiguous chunk of data
+ fetched from memory. Each time data is brought into the cache, an entire
+ line is read at once. The data loaded into a cache line is always aligned
+ on a boundary equal to the line size. */
+/* #define INSN_CACHE_LINE_WIDTH */
+
+/* The number of alternative cache lines that can hold any particular memory
+ location. */
+/* #define INSN_CACHE_DEPTH */
+
+/* Alternatively, if the machine has system calls or instructions to clear the
+ instruction cache directly, you can define the following macro. */
+
+/* If defined, expands to a C expression clearing the *instruction cache* in
+ the specified interval. If it is not defined, and the macro INSN_CACHE_SIZE
+ is defined, some generic code is generated to clear the cache. The
+ definition of this macro would typically be a series of `asm' statements.
+ Both BEG and END are both pointer expressions. */
+/* #define CLEAR_INSN_CACHE (BEG, END) */
+
+/* To use a standard subroutine, define the following macro. In addition, you
+ must make sure that the instructions in a trampoline fill an entire cache
+ line with identical instructions, or else ensure that the beginning of the
+ trampoline code is always aligned at the same point in its cache line. Look
+ in `m68k.h' as a guide. */
+
+/* Define this macro if trampolines need a special subroutine to do their work.
+ The macro should expand to a series of `asm' statements which will be
+ compiled with GNU CC. They go in a library function named
+ `__transfer_from_trampoline'.
+
+ If you need to avoid executing the ordinary prologue code of a compiled C
+ function when you jump to the subroutine, you can do so by placing a special
+ label of your own in the assembler code. Use one `asm' statement to
+ generate an assembler label, and another to make the label global. Then
+ trampolines can use that label to jump directly to your special assembler
+ code. */
+/* #define TRANSFER_FROM_TRAMPOLINE */
+
+/*}}}*/ \f
+/*{{{ Implicit Calls to Library Routines */
+
+/* A C string constant giving the name of the function to call for
+ multiplication of one signed full-word by another. If you do not define
+ this macro, the default name is used, which is `__mulsi3', a function
+ defined in `libgcc.a'. */
+/* #define MULSI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for division of
+ one signed full-word by another. If you do not define this macro, the
+ default name is used, which is `__divsi3', a function defined in `libgcc.a'. */
+/* #define DIVSI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for division of
+ one unsigned full-word by another. If you do not define this macro, the
+ default name is used, which is `__udivsi3', a function defined in
+ `libgcc.a'. */
+/* #define UDIVSI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for the
+ remainder in division of one signed full-word by another. If you do not
+ define this macro, the default name is used, which is `__modsi3', a function
+ defined in `libgcc.a'. */
+/* #define MODSI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for the
+ remainder in division of one unsigned full-word by another. If you do not
+ define this macro, the default name is used, which is `__umodsi3', a
+ function defined in `libgcc.a'. */
+/* #define UMODSI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for
+ multiplication of one signed double-word by another. If you do not define
+ this macro, the default name is used, which is `__muldi3', a function
+ defined in `libgcc.a'. */
+/* #define MULDI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for division of
+ one signed double-word by another. If you do not define this macro, the
+ default name is used, which is `__divdi3', a function defined in `libgcc.a'. */
+/* #define DIVDI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for division of
+ one unsigned full-word by another. If you do not define this macro, the
+ default name is used, which is `__udivdi3', a function defined in
+ `libgcc.a'. */
+/* #define UDIVDI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for the
+ remainder in division of one signed double-word by another. If you do not
+ define this macro, the default name is used, which is `__moddi3', a function
+ defined in `libgcc.a'. */
+/* #define MODDI3_LIBCALL */
+
+/* A C string constant giving the name of the function to call for the
+ remainder in division of one unsigned full-word by another. If you do not
+ define this macro, the default name is used, which is `__umoddi3', a
+ function defined in `libgcc.a'. */
+/* #define UMODDI3_LIBCALL */
+
+/* Define this macro as a C statement that declares additional library routines
+ renames existing ones. `init_optabs' calls this macro after initializing all
+ the normal library routines. */
+/* #define INIT_TARGET_OPTABS */
+
+/* The value of `EDOM' on the target machine, as a C integer constant
+ expression. If you don't define this macro, GNU CC does not attempt to
+ deposit the value of `EDOM' into `errno' directly. Look in
+ `/usr/include/errno.h' to find the value of `EDOM' on your system.
+
+ If you do not define `TARGET_EDOM', then compiled code reports domain errors
+ by calling the library function and letting it report the error. If
+ mathematical functions on your system use `matherr' when there is an error,
+ then you should leave `TARGET_EDOM' undefined so that `matherr' is used
+ normally. */
+/* #define TARGET_EDOM */
+
+/* Define this macro as a C expression to create an rtl expression that refers
+ to the global "variable" `errno'. (On certain systems, `errno' may not
+ actually be a variable.) If you don't define this macro, a reasonable
+ default is used. */
+/* #define GEN_ERRNO_RTX */
+
+/* Define this macro if GNU CC should generate calls to the System V (and ANSI
+ C) library functions `memcpy' and `memset' rather than the BSD functions
+ `bcopy' and `bzero'.
+
+ Defined in svr4.h. */
+#define TARGET_MEM_FUNCTIONS
+
+/* Define this macro if only `float' arguments cannot be passed to library
+ routines (so they must be converted to `double'). This macro affects both
+ how library calls are generated and how the library routines in `libgcc1.c'
+ accept their arguments. It is useful on machines where floating and fixed
+ point arguments are passed differently, such as the i860. */
+/* #define LIBGCC_NEEDS_DOUBLE */
+
+/* Define this macro to override the type used by the library routines to pick
+ up arguments of type `float'. (By default, they use a union of `float' and
+ `int'.)
+
+ The obvious choice would be `float'--but that won't work with traditional C
+ compilers that expect all arguments declared as `float' to arrive as
+ `double'. To avoid this conversion, the library routines ask for the value
+ as some other type and then treat it as a `float'.
+
+ On some systems, no other type will work for this. For these systems, you
+ must use `LIBGCC_NEEDS_DOUBLE' instead, to force conversion of the values
+ `double' before they are passed. */
+/* #define FLOAT_ARG_TYPE */
+
+/* Define this macro to override the way library routines redesignate a `float'
+ argument as a `float' instead of the type it was passed as. The default is
+ an expression which takes the `float' field of the union. */
+/* #define FLOATIFY(PASSED_VALUE) */
+
+/* Define this macro to override the type used by the library routines to
+ return values that ought to have type `float'. (By default, they use
+ `int'.)
+
+ The obvious choice would be `float'--but that won't work with traditional C
+ compilers gratuitously convert values declared as `float' into `double'. */
+/* #define FLOAT_VALUE_TYPE */
+
+/* Define this macro to override the way the value of a `float'-returning
+ library routine should be packaged in order to return it. These functions
+ are actually declared to return type `FLOAT_VALUE_TYPE' (normally `int').
+
+ These values can't be returned as type `float' because traditional C
+ compilers would gratuitously convert the value to a `double'.
+
+ A local variable named `intify' is always available when the macro `INTIFY'
+ is used. It is a union of a `float' field named `f' and a field named `i'
+ whose type is `FLOAT_VALUE_TYPE' or `int'.
+
+ If you don't define this macro, the default definition works by copying the
+ value through that union. */
+/* #define INTIFY(FLOAT_VALUE) */
+
+/* Define this macro as the name of the data type corresponding to `SImode' in
+ the system's own C compiler.
+
+ You need not define this macro if that type is `long int', as it usually is. */
+/* #define nongcc_SI_type */
+
+/* Define this macro as the name of the data type corresponding to the
+ word_mode in the system's own C compiler.
+
+ You need not define this macro if that type is `long int', as it usually is. */
+/* #define nongcc_word_type */
+
+/* Define these macros to supply explicit C statements to carry out various
+ arithmetic operations on types `float' and `double' in the library routines
+ in `libgcc1.c'. See that file for a full list of these macros and their
+ arguments.
+
+ On most machines, you don't need to define any of these macros, because the
+ C compiler that comes with the system takes care of doing them. */
+/* #define perform_... */
+
+/* Define this macro to generate code for Objective C message sending using the
+ calling convention of the NeXT system. This calling convention involves
+ passing the object, the selector and the method arguments all at once to the
+ method-lookup library function.
+
+ The default calling convention passes just the object and the selector to
+ the lookup function, which returns a pointer to the method. */
+/* #define NEXT_OBJC_RUNTIME */
+
+/*}}}*/ \f
+/*{{{ Addressing Modes */
+
+/* Define this macro if the machine supports post-increment addressing. */
+/* #define HAVE_POST_INCREMENT 0 */
+
+/* Similar for other kinds of addressing. */
+/* #define HAVE_PRE_INCREMENT 0 */
+/* #define HAVE_POST_DECREMENT 0 */
+/* #define HAVE_PRE_DECREMENT 0 */
+
+/* A C expression that is 1 if the RTX X is a constant which is a valid
+ address. On most machines, this can be defined as `CONSTANT_P (X)', but a
+ few machines are more restrictive in which constant addresses are supported.
+
+ `CONSTANT_P' 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. */
+#define CONSTANT_ADDRESS_P(X) CONSTANT_P (X)
+
+/* 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 `GO_IF_LEGITIMATE_ADDRESS' would ever accept. */
+#define MAX_REGS_PER_ADDRESS 1
+
+/* A C compound statement with a conditional `goto LABEL;' executed if X (an
+ RTX) is a legitimate memory address on the target machine for a memory
+ operand of mode MODE.
+
+ It usually pays to define several simpler macros to serve as subroutines for
+ this one. Otherwise it may be too complicated to understand.
+
+ This macro must exist in two variants: a strict variant and a non-strict
+ one. 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. In contexts where some kind of register is
+ required, a pseudo-register with no hard register must be rejected.
+
+ 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.
+
+ Compiler source files that want to use the strict variant of this macro
+ define the macro `REG_OK_STRICT'. You should use an `#ifdef REG_OK_STRICT'
+ conditional to define the strict variant in that case and the non-strict
+ variant otherwise.
+
+ Subroutines to check for acceptable registers for various purposes (one for
+ base registers, one for index registers, and so on) are typically among the
+ subroutines used to define `GO_IF_LEGITIMATE_ADDRESS'. Then only these
+ subroutine macros need have two variants; the higher levels of macros may be
+ the same whether strict or not.
+
+ 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 macro
+ `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.
+
+ The best way to modify the name string is by adding text to the beginning,
+ with suitable punctuation to prevent any ambiguity. Allocate the new name
+ in `saveable_obstack'. You will have to modify `ASM_OUTPUT_LABELREF' to
+ remove and decode the added text and output the name accordingly, and define
+ `STRIP_NAME_ENCODING' to access the original name string.
+
+ You can check the information stored here into the `symbol_ref' in the
+ definitions of the macros `GO_IF_LEGITIMATE_ADDRESS' and
+ `PRINT_OPERAND_ADDRESS'.
+
+ Used in explow.c, recog.c, reload.c. */
+
+/* On the FR30 we only have one real addressing mode - an address in a
+ register. There are three special cases however:
+
+ * indexed addressing using small positive offsets from the stack pointer
+
+ * indexed addressing using small signed offsets from the frame pointer
+
+ * register plus register addresing using R13 as the base register.
+
+ At the moment we only support the first two of these special cases. */
+
+#ifdef REG_OK_STRICT
+#define GO_IF_LEGITIMATE_ADDRESS(MODE, X, LABEL) \
+ do \
+ { \
+ if (GET_CODE (X) == REG && REG_OK_FOR_BASE_P (X)) \
+ goto LABEL; \
+ if (GET_CODE (X) == PLUS \
+ && ((MODE) == SImode || (MODE) == SFmode) \
+ && XEXP (X, 0) == stack_pointer_rtx \
+ && GET_CODE (XEXP (X, 1)) == CONST_INT \
+ && IN_RANGE (INTVAL (XEXP (X, 1)), 0, (1 << 6) - 4)) \
+ goto LABEL; \
+ if (GET_CODE (X) == PLUS \
+ && ((MODE) == SImode || (MODE) == SFmode) \
+ && XEXP (X, 0) == frame_pointer_rtx \
+ && GET_CODE (XEXP (X, 1)) == CONST_INT \
+ && IN_RANGE (INTVAL (XEXP (X, 1)), -(1 << 9), (1 << 9) - 4)) \
+ goto LABEL; \
+ } \
+ while (0)
+#else
+#define GO_IF_LEGITIMATE_ADDRESS(MODE, X, LABEL) \
+ do \
+ { \
+ if (GET_CODE (X) == REG && REG_OK_FOR_BASE_P (X)) \
+ goto LABEL; \
+ if (GET_CODE (X) == PLUS \
+ && ((MODE) == SImode || (MODE) == SFmode) \
+ && XEXP (X, 0) == stack_pointer_rtx \
+ && GET_CODE (XEXP (X, 1)) == CONST_INT \
+ && IN_RANGE (INTVAL (XEXP (X, 1)), 0, (1 << 6) - 4)) \
+ goto LABEL; \
+ if (GET_CODE (X) == PLUS \
+ && ((MODE) == SImode || (MODE) == SFmode) \
+ && (XEXP (X, 0) == frame_pointer_rtx \
+ || XEXP(X,0) == arg_pointer_rtx) \
+ && GET_CODE (XEXP (X, 1)) == CONST_INT \
+ && IN_RANGE (INTVAL (XEXP (X, 1)), -(1 << 9), (1 << 9) - 4)) \
+ goto LABEL; \
+ } \
+ while (0)
+#endif
+
+/* A C expression that is nonzero if X (assumed to be a `reg' RTX) is valid for
+ use as a base register. For hard registers, it should always accept those
+ which the hardware permits and reject the others. Whether the macro accepts
+ or rejects pseudo registers must be controlled by `REG_OK_STRICT' as
+ described above. This usually requires two variant definitions, of which
+ `REG_OK_STRICT' controls the one actually used. */
+#ifdef REG_OK_STRICT
+#define REG_OK_FOR_BASE_P(X) (((unsigned) REGNO (X)) <= STACK_POINTER_REGNUM)
+#else
+#define REG_OK_FOR_BASE_P(X) 1
+#endif
+
+/* A C expression that is nonzero if X (assumed to be a `reg' RTX) is valid for
+ use as an index register.
+
+ The difference between an index register and a base register is that the
+ index register may be scaled. If an address involves the sum of two
+ registers, neither one of them scaled, then either one may be labeled the
+ "base" and the other the "index"; but whichever labeling is used must fit
+ the machine's constraints of which registers may serve in each capacity.
+ The compiler will try both labelings, looking for one that is valid, and
+ will reload one or both registers only if neither labeling works. */
+#define REG_OK_FOR_INDEX_P(X) REG_OK_FOR_BASE_P (X)
+
+/* A C compound statement that attempts to replace X with a valid memory
+ address for an operand of mode MODE. WIN will be a C statement label
+ elsewhere in the code; the macro definition may use
+
+ GO_IF_LEGITIMATE_ADDRESS (MODE, X, WIN);
+
+ to avoid further processing if the address has become legitimate.
+
+ 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 generated by this macro should 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.
+
+ It is not necessary for this macro to come up with a legitimate address.
+ The compiler has standard ways of doing so in all cases. In fact, it is
+ safe for this macro to do nothing. But often a machine-dependent strategy
+ can generate better code. */
+#define LEGITIMIZE_ADDRESS(X, OLDX, MODE, WIN)
+
+/* 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. */
+#define GO_IF_MODE_DEPENDENT_ADDRESS(ADDR, LABEL)
+
+/* 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. */
+#define LEGITIMATE_CONSTANT_P(X) 1
+
+/*}}}*/ \f
+/*{{{ Condition Code Status */
+
+/* C code for a data type which is used for declaring the `mdep' component of
+ `cc_status'. It defaults to `int'.
+
+ This macro is not used on machines that do not use `cc0'. */
+/* #define CC_STATUS_MDEP */
+
+/* A C expression to initialize the `mdep' field to "empty". The default
+ definition does nothing, since most machines don't use the field anyway. If
+ you want to use the field, you should probably define this macro to
+ initialize it.
+
+ This macro is not used on machines that do not use `cc0'. */
+/* #define CC_STATUS_MDEP_INIT */
+
+/* A C compound statement to set the components of `cc_status' appropriately
+ for an insn INSN whose body is EXP. It is this macro's responsibility to
+ recognize insns that set the condition code as a byproduct of other activity
+ as well as those that explicitly set `(cc0)'.
+
+ This macro is not used on machines that do not use `cc0'.
+
+ If there are insns that do not set the condition code but do alter other
+ machine registers, this macro must check to see whether they invalidate the
+ expressions that the condition code is recorded as reflecting. For example,
+ on the 68000, insns that store in address registers do not set the condition
+ code, which means that usually `NOTICE_UPDATE_CC' can leave `cc_status'
+ unaltered for such insns. But suppose that the previous insn set the
+ condition code based on location `a4@(102)' and the current insn stores a
+ new value in `a4'. Although the condition code is not changed by this, it
+ will no longer be true that it reflects the contents of `a4@(102)'.
+ Therefore, `NOTICE_UPDATE_CC' must alter `cc_status' in this case to say
+ that nothing is known about the condition code value.
+
+ The definition of `NOTICE_UPDATE_CC' must be prepared to deal with the
+ results of peephole optimization: insns whose patterns are `parallel' RTXs
+ containing various `reg', `mem' or constants which are just the operands.
+ The RTL structure of these insns is not sufficient to indicate what the
+ insns actually do. What `NOTICE_UPDATE_CC' should do when it sees one is
+ just to run `CC_STATUS_INIT'.
+
+ A possible definition of `NOTICE_UPDATE_CC' is to call a function that looks
+ at an attribute named, for example, `cc'. This
+ avoids having detailed information about patterns in two places, the `md'
+ file and in `NOTICE_UPDATE_CC'. */
+/* #define NOTICE_UPDATE_CC(EXP, INSN) fr30_notice_update_cc (INSN)
+ extern int fr30_notice_update_cc PROTO ((Rtx)); */
+
+/* A list of names to be used for additional modes for condition code values in
+ registers. These names are added to `enum
+ machine_mode' and all have class `MODE_CC'. By convention, they should
+ start with `CC' and end with `mode'.
+
+ You should only define this macro if your machine does not use `cc0' and
+ only if additional modes are required. */
+/* #define EXTRA_CC_MODES */
+
+/* A list of C strings giving the names for the modes listed in
+ `EXTRA_CC_MODES'. For example, the Sparc defines this macro and
+ `EXTRA_CC_MODES' as
+
+ #define EXTRA_CC_MODES CC_NOOVmode, CCFPmode, CCFPEmode
+ #define EXTRA_CC_NAMES "CC_NOOV", "CCFP", "CCFPE"
+
+ This macro is not required if `EXTRA_CC_MODES' is not defined. */
+/* #define EXTRA_CC_NAMES */
+
+/* Returns a mode from class `MODE_CC' to be used when comparison operation
+ code OP is applied to rtx X and Y. For example, on the Sparc,
+ `SELECT_CC_MODE' is defined as (see *note Jump Patterns::. for a
+ description of the reason for this definition)
+
+ #define SELECT_CC_MODE(OP,X,Y) \
+ (GET_MODE_CLASS (GET_MODE (X)) == MODE_FLOAT \
+ ? ((OP == EQ || OP == NE) ? CCFPmode : CCFPEmode) \
+ : ((GET_CODE (X) == PLUS || GET_CODE (X) == MINUS \
+ || GET_CODE (X) == NEG) \
+ ? CC_NOOVmode : CCmode))
+
+ You need not define this macro if `EXTRA_CC_MODES' is not defined. */
+/* #define SELECT_CC_MODE(OP, X, Y) */
+
+/* One some machines not all possible comparisons are defined, but you can
+ convert an invalid comparison into a valid one. For example, the Alpha does
+ not have a `GT' comparison, but you can use an `LT' comparison instead and
+ swap the order of the operands.
+
+ On such machines, define this macro to be a C statement to do any required
+ conversions. CODE is the initial comparison code and OP0 and OP1 are the
+ left and right operands of the comparison, respectively. You should modify
+ CODE, OP0, and OP1 as required.
+
+ GNU CC will not assume that the comparison resulting from this macro is
+ valid but will see if the resulting insn matches a pattern in the `md' file.
+
+ You need not define this macro if it would never change the comparison code
+ or operands. */
+/* #define CANONICALIZE_COMPARISON(CODE, OP0, OP1) */
+
+/* A C expression whose value is one if it is always safe to reverse a
+ comparison whose mode is MODE. If `SELECT_CC_MODE' can ever return MODE for
+ a floating-point inequality comparison, then `REVERSIBLE_CC_MODE (MODE)'
+ must be zero.
+
+ You need not define this macro if it would always returns zero or if the
+ floating-point format is anything other than `IEEE_FLOAT_FORMAT'. For
+ example, here is the definition used on the Sparc, where floating-point
+ inequality comparisons are always given `CCFPEmode':
+
+ #define REVERSIBLE_CC_MODE(MODE) ((MODE) != CCFPEmode) */
+/* #define REVERSIBLE_CC_MODE(MODE) */
+
+/*}}}*/ \f
+/*{{{ Describing Relative Costs of Operations */
+
+/* A part of a C `switch' statement that describes the relative costs of
+ constant RTL expressions. It must contain `case' labels for expression
+ codes `const_int', `const', `symbol_ref', `label_ref' and `const_double'.
+ Each case must ultimately reach a `return' statement to return the relative
+ cost of the use of that kind of constant value in an expression. The cost
+ may depend on the precise value of the constant, which is available for
+ examination in X, and the rtx code of the expression in which it is
+ contained, found in OUTER_CODE.
+
+ CODE is the expression code--redundant, since it can be obtained with
+ `GET_CODE (X)'. */
+/* #define CONST_COSTS(X, CODE, OUTER_CODE) */
+
+/* Like `CONST_COSTS' but applies to nonconstant RTL expressions. This can be
+ used, for example, to indicate how costly a multiply instruction is. In
+ writing this macro, you can use the construct `COSTS_N_INSNS (N)' to specify
+ a cost equal to N fast instructions. OUTER_CODE is the code of the
+ expression in which X is contained.
+
+ This macro is optional; do not define it if the default cost assumptions are
+ adequate for the target machine. */
+/* #define RTX_COSTS(X, CODE, OUTER_CODE) */
+
+/* An expression giving the cost of an addressing mode that contains ADDRESS.
+ If not defined, the cost is computed from the ADDRESS expression and the
+ `CONST_COSTS' values.
+
+ For most CISC machines, the default cost is a good approximation of the true
+ cost of the addressing mode. However, on RISC machines, all instructions
+ normally have the same length and execution time. Hence all addresses will
+ have equal costs.
+
+ In cases where more than one form of an address is known, the form with the
+ lowest cost will be used. If multiple forms have the same, lowest, cost,
+ the one that is the most complex will be used.
+
+ For example, suppose an address that is equal to the sum of a register and a
+ constant is used twice in the same basic block. When this macro is not
+ defined, the address will be computed in a register and memory references
+ will be indirect through that register. On machines where the cost of the
+ addressing mode containing the sum is no higher than that of a simple
+ indirect reference, this will produce an additional instruction and possibly
+ require an additional register. Proper specification of this macro
+ eliminates this overhead for such machines.
+
+ Similar use of this macro is made in strength reduction of loops.
+
+ ADDRESS need not be valid as an address. In such a case, the cost is not
+ relevant and can be any value; invalid addresses need not be assigned a
+ different cost.
+
+ On machines where an address involving more than one register is as cheap as
+ an address computation involving only one register, defining `ADDRESS_COST'
+ to reflect this can cause two registers to be live over a region of code
+ where only one would have been if `ADDRESS_COST' were not defined in that
+ manner. This effect should be considered in the definition of this macro.
+ Equivalent costs should probably only be given to addresses with different
+ numbers of registers on machines with lots of registers.
+
+ This macro will normally either not be defined or be defined as a constant. */
+/* #define ADDRESS_COST(ADDRESS) */
+
+/* A C expression for the cost of moving data from a register in class FROM to
+ one in class TO. The classes are expressed using the enumeration values
+ such as `GENERAL_REGS'. A value of 4 is the default; other values are
+ interpreted relative to that.
+
+ It is not required that the cost always equal 2 when FROM is the same as TO;
+ on some machines it is expensive to move between registers if they are not
+ general registers.
+
+ If reload sees an insn consisting of a single `set' between two hard
+ registers, and if `REGISTER_MOVE_COST' applied to their classes returns a
+ value of 2, reload does not check to ensure that the constraints of the insn
+ are met. Setting a cost of other than 2 will allow reload to verify that
+ the constraints are met. You should do this if the `movM' pattern's
+ constraints do not allow such copying. */
+/* #define REGISTER_MOVE_COST(FROM, TO) */
+
+/* A C expression for the cost of moving data of mode M between a register and
+ memory. A value of 2 is the default; this cost is relative to those in
+ `REGISTER_MOVE_COST'.
+
+ If moving between registers and memory is more expensive than between two
+ registers, you should define this macro to express the relative cost. */
+/* #define MEMORY_MOVE_COST(M,C,I) */
+
+/* A C expression for the cost of a branch instruction. A value of 1 is the
+ default; other values are interpreted relative to that. */
+
+/* Here are additional macros which do not specify precise relative costs, but
+ only that certain actions are more expensive than GNU CC would ordinarily
+ expect. */
+
+/* #define BRANCH_COST */
+
+/* Define this macro as a C expression which is nonzero if accessing less than
+ a word of memory (i.e. a `char' or a `short') is no faster than accessing a
+ word of memory, i.e., if such access require more than one instruction or if
+ there is no difference in cost between byte and (aligned) word loads.
+
+ When this macro is not defined, the compiler will access a field by finding
+ the smallest containing object; when it is defined, a fullword load will be
+ used if alignment permits. Unless bytes accesses are faster than word
+ accesses, using word accesses is preferable since it may eliminate
+ subsequent memory access if subsequent accesses occur to other fields in the
+ same word of the structure, but to different bytes. */
+#define SLOW_BYTE_ACCESS 1
+
+/* Define this macro if zero-extension (of a `char' or `short' to an `int') can
+ be done faster if the destination is a register that is known to be zero.
+
+ If you define this macro, you must have instruction patterns that recognize
+ RTL structures like this:
+
+ (set (strict_low_part (subreg:QI (reg:SI ...) 0)) ...)
+
+ and likewise for `HImode'. */
+#define SLOW_ZERO_EXTEND 0
+
+/* Define this macro to be the value 1 if unaligned accesses have a cost many
+ times greater than aligned accesses, for example if they are emulated in a
+ trap handler.
+
+ When this macro is non-zero, the compiler will act as if `STRICT_ALIGNMENT'
+ were non-zero when generating code for block moves. This can cause
+ significantly more instructions to be produced. Therefore, do not set this
+ macro non-zero if unaligned accesses only add a cycle or two to the time for
+ a memory access.
+
+ If the value of this macro is always zero, it need not be defined. */
+/* #define SLOW_UNALIGNED_ACCESS */
+
+/* Define this macro to inhibit strength reduction of memory addresses. (On
+ some machines, such strength reduction seems to do harm rather than good.) */
+/* #define DONT_REDUCE_ADDR */
+
+/* The number of scalar move insns which should be generated instead of a
+ string move insn or a library call. Increasing the value will always make
+ code faster, but eventually incurs high cost in increased code size.
+
+ If you don't define this, a reasonable default is used. */
+/* #define MOVE_RATIO */
+
+/* Define this macro if it is as good or better to call a constant function
+ address than to call an address kept in a register. */
+/* #define NO_FUNCTION_CSE */
+
+/* Define this macro if it is as good or better for a function to call itself
+ with an explicit address than to call an address kept in a register. */
+/* #define NO_RECURSIVE_FUNCTION_CSE */
+
+/* A C statement (sans semicolon) to update the integer variable COST based on
+ the relationship between INSN that is dependent on DEP_INSN through the
+ dependence LINK. The default is to make no adjustment to COST. This can be
+ used for example to specify to the scheduler that an output- or
+ anti-dependence does not incur the same cost as a data-dependence. */
+/* #define ADJUST_COST(INSN, LINK, DEP_INSN, COST) */
+
+/* A C statement (sans semicolon) to update the integer scheduling
+ priority `INSN_PRIORITY(INSN)'. Reduce the priority to execute
+ the INSN earlier, increase the priority to execute INSN later.
+ Do not define this macro if you do not need to adjust the
+ scheduling priorities of insns. */
+/* #define ADJUST_PRIORITY (INSN) */
+
+/*}}}*/ \f
+/*{{{ Dividing the output into sections. */
+
+/* A C expression whose value is a string containing the assembler operation
+ that should precede instructions and read-only data. Normally `".text"' is
+ right. */
+#define TEXT_SECTION_ASM_OP ".text"
+
+/* A C expression whose value is a string containing the assembler operation to
+ identify the following data as writable initialized data. Normally
+ `".data"' is right. */
+#define DATA_SECTION_ASM_OP ".data"
+
+/* if defined, a C expression whose value is a string containing the assembler
+ operation to identify the following data as shared data. If not defined,
+ `DATA_SECTION_ASM_OP' will be used. */
+/* #define SHARED_SECTION_ASM_OP */
+
+/* If defined, a C expression whose value is a string containing the
+ assembler operation to identify the following data as
+ uninitialized global data. If not defined, and neither
+ `ASM_OUTPUT_BSS' nor `ASM_OUTPUT_ALIGNED_BSS' are defined,
+ uninitialized global data will be output in the data section if
+ `-fno-common' is passed, otherwise `ASM_OUTPUT_COMMON' will be
+ used. */
+#define BSS_SECTION_ASM_OP ".bss"
+
+/* If defined, a C expression whose value is a string containing the
+ assembler operation to identify the following data as
+ uninitialized global shared data. If not defined, and
+ `BSS_SECTION_ASM_OP' is, the latter will be used. */
+/* #define SHARED_BSS_SECTION_ASM_OP */
+
+/* A list of names for sections other than the standard two, which are
+ `in_text' and `in_data'. You need not define this macro on a system with no
+ other sections (that GCC needs to use).
+
+ Defined in svr4.h. */
+/* #define EXTRA_SECTIONS */
+
+/* One or more functions to be defined in `varasm.c'. These functions should
+ do jobs analogous to those of `text_section' and `data_section', for your
+ additional sections. Do not define this macro if you do not define
+ `EXTRA_SECTIONS'.
+
+ Defined in svr4.h. */
+/* #define EXTRA_SECTION_FUNCTIONS */
+
+/* On most machines, read-only variables, constants, and jump tables are placed
+ in the text section. If this is not the case on your machine, this macro
+ should be defined to be the name of a function (either `data_section' or a
+ function defined in `EXTRA_SECTIONS') that switches to the section to be
+ used for read-only items.
+
+ If these items should be placed in the text section, this macro should not
+ be defined. */
+/* #define READONLY_DATA_SECTION */
+
+/* A C statement or statements to switch to the appropriate section for output
+ of EXP. You can assume that EXP is either a `VAR_DECL' node or a constant
+ of some sort. RELOC indicates whether the initial value of EXP requires
+ link-time relocations. Select the section by calling `text_section' or one
+ of the alternatives for other sections.
+
+ Do not define this macro if you put all read-only variables and constants in
+ the read-only data section (usually the text section).
+
+ Defined in svr4.h. */
+/* #define SELECT_SECTION(EXP, RELOC) */
+
+/* A C statement or statements to switch to the appropriate section for output
+ of RTX in mode MODE. You can assume that RTX is some kind of constant in
+ RTL. The argument MODE is redundant except in the case of a `const_int'
+ rtx. Select the section by calling `text_section' or one of the
+ alternatives for other sections.
+
+ Do not define this macro if you put all constants in the read-only data
+ section.
+
+ Defined in svr4.h. */
+/* #define SELECT_RTX_SECTION(MODE, RTX) */
+
+/* Define this macro if jump tables (for `tablejump' insns) should be output in
+ the text section, along with the assembler instructions. Otherwise, the
+ readonly data section is used.
+
+ This macro is irrelevant if there is no separate readonly data section. */
+/* #define JUMP_TABLES_IN_TEXT_SECTION */
+
+/* Define this macro if references to a symbol must be treated differently
+ depending on something about the variable or function named by the symbol
+ (such as what section it is in).
+
+ The macro definition, if any, is executed immediately after the rtl for DECL
+ has been created and stored in `DECL_RTL (DECL)'. The value of the rtl will
+ be a `mem' whose address is a `symbol_ref'.
+
+ The usual thing for this macro to do is to record a flag in the `symbol_ref'
+ (such as `SYMBOL_REF_FLAG') or to store a modified name string in the
+ `symbol_ref' (if one bit is not enough information). */
+/* #define ENCODE_SECTION_INFO(DECL) */
+
+/* Decode SYM_NAME and store the real name part in VAR, sans the characters
+ that encode section info. Define this macro if `ENCODE_SECTION_INFO' alters
+ the symbol's name string. */
+/* #define STRIP_NAME_ENCODING(VAR, SYM_NAME) */
+
+/* A C expression which evaluates to true if DECL should be placed
+ into a unique section for some target-specific reason. If you do
+ not define this macro, the default is `0'. Note that the flag
+ `-ffunction-sections' will also cause functions to be placed into
+ unique sections.
+
+ Defined in svr4.h. */
+/* #define UNIQUE_SECTION_P(DECL) */
+
+/* A C statement to build up a unique section name, expressed as a
+ STRING_CST node, and assign it to `DECL_SECTION_NAME (DECL)'.
+ RELOC indicates whether the initial value of EXP requires
+ link-time relocations. If you do not define this macro, GNU CC
+ will use the symbol name prefixed by `.' as the section name.
+
+ Defined in svr4.h. */
+/* #define UNIQUE_SECTION(DECL, RELOC) */
+
+/*}}}*/ \f
+/*{{{ Position Independent Code. */
+
+/* The register number of the register used to address a table of static data
+ addresses in memory. In some cases this register is defined by a
+ processor's "application binary interface" (ABI). When this macro is
+ defined, RTL is generated for this register once, as with the stack pointer
+ and frame pointer registers. If this macro is not defined, it is up to the
+ machine-dependent files to allocate such a register (if necessary). */
+/* #define PIC_OFFSET_TABLE_REGNUM */
+
+/* Define this macro if the register defined by `PIC_OFFSET_TABLE_REGNUM' is
+ clobbered by calls. Do not define this macro if `PPIC_OFFSET_TABLE_REGNUM'
+ is not defined. */
+/* #define PIC_OFFSET_TABLE_REG_CALL_CLOBBERED */
+
+/* By generating position-independent code, when two different programs (A and
+ B) share a common library (libC.a), the text of the library can be shared
+ whether or not the library is linked at the same address for both programs.
+ In some of these environments, position-independent code requires not only
+ the use of different addressing modes, but also special code to enable the
+ use of these addressing modes.
+
+ The `FINALIZE_PIC' macro serves as a hook to emit these special codes once
+ the function is being compiled into assembly code, but not before. (It is
+ not done before, because in the case of compiling an inline function, it
+ would lead to multiple PIC prologues being included in functions which used
+ inline functions and were compiled to assembly language.) */
+/* #define FINALIZE_PIC */
+
+/* A C expression that is nonzero if X is a legitimate immediate operand on the
+ target machine when generating position independent code. You can assume
+ that X satisfies `CONSTANT_P', so you need not check this. You can also
+ assume FLAG_PIC is true, so you need not check it either. You need not
+ define this macro if all constants (including `SYMBOL_REF') can be immediate
+ operands when generating position independent code. */
+/* #define LEGITIMATE_PIC_OPERAND_P(X) */
+
+/*}}}*/ \f
+/*{{{ The Overall Framework of an Assembler File. */
+
+/* A C expression which outputs to the stdio stream STREAM some appropriate
+ text to go at the end of an assembler file.
+
+ If this macro is not defined, the default is to output nothing special at
+ the end of the file. Most systems don't require any definition.
+
+ On systems that use SDB, it is necessary to output certain commands; see
+ `attasm.h'.
+
+ Defined in svr4.h. */
+/* #define ASM_FILE_END(STREAM) */
+
+/* A C statement to output assembler commands which will identify the object
+ file as having been compiled with GNU CC (or another GNU compiler).
+
+ If you don't define this macro, the string `gcc_compiled.:' is output. This
+ string is calculated to define a symbol which, on BSD systems, will never be
+ defined for any other reason. GDB checks for the presence of this symbol
+ when reading the symbol table of an executable.
+
+ On non-BSD systems, you must arrange communication with GDB in some other
+ fashion. If GDB is not used on your system, you can define this macro with
+ an empty body.
+
+ Defined in svr4.h. */
+/* #define ASM_IDENTIFY_GCC(FILE) */
+
+/* Like ASM_IDENTIFY_GCC, but used when dbx debugging is selected to emit
+ a stab the debugger uses to identify gcc as the compiler that is emitted
+ after the stabs for the filename, which makes it easier for GDB to parse.
+
+ Defined in svr4.h. */
+/* #define ASM_IDENTIFY_GCC_AFTER_SOURCE(FILE) */
+
+/* A C string constant describing how to begin a comment in the target
+ assembler language. The compiler assumes that the comment will end at the
+ end of the line. */
+#define ASM_COMMENT_START ";"
+
+/* A C string constant for text to be output before each `asm' statement or
+ group of consecutive ones. Normally this is `"#APP"', which is a comment
+ that has no effect on most assemblers but tells the GNU assembler that it
+ must check the lines that follow for all valid assembler constructs. */
+#define ASM_APP_ON "#APP\n"
+
+/* A C string constant for text to be output after each `asm' statement or
+ group of consecutive ones. Normally this is `"#NO_APP"', which tells the
+ GNU assembler to resume making the time-saving assumptions that are valid
+ for ordinary compiler output. */
+#define ASM_APP_OFF "#NO_APP\n"
+
+/* A C statement to output COFF information or DWARF debugging information
+ which indicates that filename NAME is the current source file to the stdio
+ stream STREAM.
+
+ This macro need not be defined if the standard form of output for the file
+ format in use is appropriate. */
+/* #define ASM_OUTPUT_SOURCE_FILENAME(STREAM, NAME) */
+
+/* A C statement to output DBX or SDB debugging information before code for
+ line number LINE of the current source file to the stdio stream STREAM.
+
+ This macro need not be defined if the standard form of debugging information
+ for the debugger in use is appropriate.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_SOURCE_LINE(STREAM, LINE) */
+
+/* A C statement to output something to the assembler file to handle a `#ident'
+ directive containing the text STRING. If this macro is not defined, nothing
+ is output for a `#ident' directive.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_IDENT(STREAM, STRING) */
+
+/* A C statement to output something to the assembler file to switch to section
+ NAME for object DECL which is either a `FUNCTION_DECL', a `VAR_DECL' or
+ `NULL_TREE'. Some target formats do not support arbitrary sections. Do not
+ define this macro in such cases.
+
+ At present this macro is only used to support section attributes. When this
+ macro is undefined, section attributes are disabled.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_SECTION_NAME(STREAM, DECL, NAME) */
+
+/* A C statement to output any assembler statements which are required to
+ precede any Objective C object definitions or message sending. The
+ statement is executed only when compiling an Objective C program. */
+/* #define OBJC_PROLOGUE */
+
+/*}}}*/ \f
+/*{{{ Output of Data. */
+
+/* A C statement to output to the stdio stream STREAM an assembler instruction
+ to assemble a floating-point constant of `TFmode', `DFmode', `SFmode',
+ `TQFmode', `HFmode', or `QFmode', respectively, whose value is VALUE. VALUE
+ will be a C expression of type `REAL_VALUE_TYPE'. Macros such as
+ `REAL_VALUE_TO_TARGET_DOUBLE' are useful for writing these definitions. */
+/* #define ASM_OUTPUT_LONG_DOUBLE(STREAM, VALUE) */
+/* #define ASM_OUTPUT_THREE_QUARTER_FLOAT(STREAM, VALUE) */
+/* #define ASM_OUTPUT_SHORT_FLOAT(STREAM, VALUE) */
+/* #define ASM_OUTPUT_BYTE_FLOAT(STREAM, VALUE) */
+
+/* This is how to output an assembler line defining a `float' constant. */
+#define ASM_OUTPUT_FLOAT(FILE, VALUE) \
+do { \
+ long t; \
+ char str[30]; \
+ REAL_VALUE_TO_TARGET_SINGLE ((VALUE), t); \
+ REAL_VALUE_TO_DECIMAL ((VALUE), "%.20e", str); \
+ fprintf (FILE, "\t.word\t0x%lx %s %s\n", \
+ t, ASM_COMMENT_START, str); \
+} while (0)
+
+/* This is how to output an assembler line defining a `double' constant. */
+#define ASM_OUTPUT_DOUBLE(FILE, VALUE) \
+do { \
+ long t[2]; \
+ char str[30]; \
+ REAL_VALUE_TO_TARGET_DOUBLE ((VALUE), t); \
+ REAL_VALUE_TO_DECIMAL ((VALUE), "%.20e", str); \
+ fprintf (FILE, "\t.word\t0x%lx %s %s\n\t.word\t0x%lx\n", \
+ t[0], ASM_COMMENT_START, str, t[1]); \
+} while (0)
+
+
+/* A C statement to output to the stdio stream STREAM an assembler instruction
+ to assemble an integer of 16, 8, 4, 2 or 1 bytes, respectively, whose value
+ is VALUE. The argument EXP will be an RTL expression which represents a
+ constant value. Use `output_addr_const (STREAM, EXP)' to output this value
+ as an assembler expression.
+
+ For sizes larger than `UNITS_PER_WORD', if the action of a macro would be
+ identical to repeatedly calling the macro corresponding to a size of
+ `UNITS_PER_WORD', once for each word, you need not define the macro. */
+/* #define ASM_OUTPUT_QUADRUPLE_INT(STREAM, EXP) */
+/* #define ASM_OUTPUT_DOUBLE_INT(STREAM, EXP) */
+
+/* This is how to output an assembler line defining a `char' constant. */
+#define ASM_OUTPUT_CHAR(FILE, VALUE) \
+do { \
+ fprintf (FILE, "\t.byte\t"); \
+ output_addr_const (FILE, (VALUE)); \
+ fprintf (FILE, "\n"); \
+} while (0)
+
+/* This is how to output an assembler line defining a `short' constant. */
+#define ASM_OUTPUT_SHORT(FILE, VALUE) \
+do { \
+ fprintf (FILE, "\t.hword\t"); \
+ output_addr_const (FILE, (VALUE)); \
+ fprintf (FILE, "\n"); \
+} while (0)
+
+/* This is how to output an assembler line defining an `int' constant.
+ We also handle symbol output here. */
+#define ASM_OUTPUT_INT(FILE, VALUE) \
+do { \
+ fprintf (FILE, "\t.word\t"); \
+ output_addr_const (FILE, (VALUE)); \
+ fprintf (FILE, "\n"); \
+} while (0)
+
+/* A C statement to output to the stdio stream STREAM an assembler instruction
+ to assemble a single byte containing the number VALUE. */
+#define ASM_OUTPUT_BYTE(STREAM, VALUE) \
+ fprintf (STREAM, "\t%s\t0x%x\n", ASM_BYTE_OP, (VALUE))
+
+/* A C string constant giving the pseudo-op to use for a sequence of
+ single-byte constants. If this macro is not defined, the default
+ is `"byte"'.
+
+ Defined in svr4.h. */
+/* #define ASM_BYTE_OP */
+
+/* A C statement to output to the stdio stream STREAM an assembler instruction
+ to assemble a string constant containing the LEN bytes at PTR. PTR will be
+ a C expression of type `char *' and LEN a C expression of type `int'.
+
+ If the assembler has a `.ascii' pseudo-op as found in the Berkeley Unix
+ assembler, do not define the macro `ASM_OUTPUT_ASCII'.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_ASCII(STREAM, PTR, LEN) */
+
+/* You may define this macro as a C expression. You should define the
+ expression to have a non-zero value if GNU CC should output the
+ constant pool for a function before the code for the function, or
+ a zero value if GNU CC should output the constant pool after the
+ function. If you do not define this macro, the usual case, GNU CC
+ will output the constant pool before the function. */
+/* #define CONSTANT_POOL_BEFORE_FUNCTION */
+
+/* A C statement to output assembler commands to define the start of the
+ constant pool for a function. FUNNAME is a string giving the name of the
+ function. Should the return type of the function be required, it can be
+ obtained via FUNDECL. SIZE is the size, in bytes, of the constant pool that
+ will be written immediately after this call.
+
+ If no constant-pool prefix is required, the usual case, this macro need not
+ be defined. */
+/* #define ASM_OUTPUT_POOL_PROLOGUE(FILE FUNNAME FUNDECL SIZE) */
+
+/* A C statement (with or without semicolon) to output a constant in the
+ constant pool, if it needs special treatment. (This macro need not do
+ anything for RTL expressions that can be output normally.)
+
+ The argument FILE is the standard I/O stream to output the assembler code
+ on. X is the RTL expression for the constant to output, and MODE is the
+ machine mode (in case X is a `const_int'). ALIGN is the required alignment
+ for the value X; you should output an assembler directive to force this much
+ alignment.
+
+ The argument LABELNO is a number to use in an internal label for the address
+ of this pool entry. The definition of this macro is responsible for
+ outputting the label definition at the proper place. Here is how to do
+ this:
+
+ ASM_OUTPUT_INTERNAL_LABEL (FILE, "LC", LABELNO);
+
+ When you output a pool entry specially, you should end with a `goto' to the
+ label JUMPTO. This will prevent the same pool entry from being output a
+ second time in the usual manner.
+
+ You need not define this macro if it would do nothing. */
+/* #define ASM_OUTPUT_SPECIAL_POOL_ENTRY(FILE, X, MODE, ALIGN, LABELNO, JUMPTO) */
+
+/* Define this macro as a C expression which is nonzero if the constant EXP, of
+ type `tree', should be output after the code for a function. The compiler
+ will normally output all constants before the function; you need not define
+ this macro if this is OK. */
+/* #define CONSTANT_AFTER_FUNCTION_P(EXP) */
+
+/* A C statement to output assembler commands to at the end of the constant
+ pool for a function. FUNNAME is a string giving the name of the function.
+ Should the return type of the function be required, you can obtain it via
+ FUNDECL. SIZE is the size, in bytes, of the constant pool that GNU CC wrote
+ immediately before this call.
+
+ If no constant-pool epilogue is required, the usual case, you need not
+ define this macro. */
+/* #define ASM_OUTPUT_POOL_EPILOGUE (FILE FUNNAME FUNDECL SIZE) */
+
+/* Define this macro as a C expression which is nonzero if C is used as a
+ logical line separator by the assembler.
+
+ If you do not define this macro, the default is that only the character `;'
+ is treated as a logical line separator. */
+/* #define IS_ASM_LOGICAL_LINE_SEPARATOR(C) */
+
+/* These macros are defined as C string constant, describing the syntax in the
+ assembler for grouping arithmetic expressions. The following definitions
+ are correct for most assemblers:
+
+ #define ASM_OPEN_PAREN "("
+ #define ASM_CLOSE_PAREN ")" */
+#define ASM_OPEN_PAREN "("
+#define ASM_CLOSE_PAREN ")"
+
+/* These macros are provided by `real.h' for writing the definitions of
+ `ASM_OUTPUT_DOUBLE' and the like: */
+
+/* These translate X, of type `REAL_VALUE_TYPE', to the target's floating point
+ representation, and store its bit pattern in the array of `long int' whose
+ address is L. The number of elements in the output array is determined by
+ the size of the desired target floating point data type: 32 bits of it go in
+ each `long int' array element. Each array element holds 32 bits of the
+ result, even if `long int' is wider than 32 bits on the host machine.
+
+ The array element values are designed so that you can print them out using
+ `fprintf' in the order they should appear in the target machine's memory. */
+/* #define REAL_VALUE_TO_TARGET_SINGLE(X, L) */
+/* #define REAL_VALUE_TO_TARGET_DOUBLE(X, L) */
+/* #define REAL_VALUE_TO_TARGET_LONG_DOUBLE(X, L) */
+
+/* This macro converts X, of type `REAL_VALUE_TYPE', to a decimal number and
+ stores it as a string into STRING. You must pass, as STRING, the address of
+ a long enough block of space to hold the result.
+
+ The argument FORMAT is a `printf'-specification that serves as a suggestion
+ for how to format the output string. */
+/* #define REAL_VALUE_TO_DECIMAL(X, FORMAT, STRING) */
+
+/*}}}*/ \f
+/*{{{ Output of Uninitialized Variables. */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM the
+ assembler definition of a common-label named NAME whose size is SIZE bytes.
+ The variable ROUNDED is the size rounded up to whatever alignment the caller
+ wants.
+
+ Use the expression `assemble_name (STREAM, NAME)' to output the name itself;
+ before and after that, output the additional assembler syntax for defining
+ the name, and a newline.
+
+ This macro controls how the assembler definitions of uninitialized global
+ variables are output. */
+/* #define ASM_OUTPUT_COMMON(STREAM, NAME, SIZE, ROUNDED) */
+
+/* Like `ASM_OUTPUT_COMMON' except takes the required alignment as a separate,
+ explicit argument. If you define this macro, it is used in place of
+ `ASM_OUTPUT_COMMON', and gives you more flexibility in handling the required
+ alignment of the variable. The alignment is specified as the number of
+ bits.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_ALIGNED_COMMON(STREAM, NAME, SIZE, ALIGNMENT) */
+
+/* Like ASM_OUTPUT_ALIGNED_COMMON except that it takes an additional argument -
+ the DECL of the variable to be output, if there is one. This macro can be
+ called with DECL == NULL_TREE. If you define this macro, it is used in
+ place of both ASM_OUTPUT_COMMON and ASM_OUTPUT_ALIGNED_COMMON, and gives you
+ more flexibility in handling the destination of the variable. */
+/* #define ASM_OUTPUT_DECL_COMMON (STREAM, DECL, NAME, SIZE, ALIGNMENT) */
+
+/* If defined, it is similar to `ASM_OUTPUT_COMMON', except that it is used
+ when NAME is shared. If not defined, `ASM_OUTPUT_COMMON' will be used. */
+/* #define ASM_OUTPUT_SHARED_COMMON(STREAM, NAME, SIZE, ROUNDED) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM the
+ assembler definition of uninitialized global DECL named NAME whose size is
+ SIZE bytes. The variable ROUNDED is the size rounded up to whatever
+ alignment the caller wants.
+
+ Try to use function `asm_output_bss' defined in `varasm.c' when defining
+ this macro. If unable, use the expression `assemble_name (STREAM, NAME)' to
+ output the name itself; before and after that, output the additional
+ assembler syntax for defining the name, and a newline.
+
+ This macro controls how the assembler definitions of uninitialized global
+ variables are output. This macro exists to properly support languages like
+ `c++' which do not have `common' data. However, this macro currently is not
+ defined for all targets. If this macro and `ASM_OUTPUT_ALIGNED_BSS' are not
+ defined then `ASM_OUTPUT_COMMON' or `ASM_OUTPUT_ALIGNED_COMMON' or
+ `ASM_OUTPUT_DECL_COMMON' is used. */
+/* #define ASM_OUTPUT_BSS(STREAM, DECL, NAME, SIZE, ROUNDED) */
+
+/* Like `ASM_OUTPUT_BSS' except takes the required alignment as a separate,
+ explicit argument. If you define this macro, it is used in place of
+ `ASM_OUTPUT_BSS', and gives you more flexibility in handling the required
+ alignment of the variable. The alignment is specified as the number of
+ bits.
+
+ Try to use function `asm_output_aligned_bss' defined in file `varasm.c' when
+ defining this macro. */
+/* #define ASM_OUTPUT_ALIGNED_BSS(STREAM, DECL, NAME, SIZE, ALIGNMENT) */
+
+/* If defined, it is similar to `ASM_OUTPUT_BSS', except that it is used when
+ NAME is shared. If not defined, `ASM_OUTPUT_BSS' will be used. */
+/* #define ASM_OUTPUT_SHARED_BSS(STREAM, DECL, NAME, SIZE, ROUNDED) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM the
+ assembler definition of a local-common-label named NAME whose size is SIZE
+ bytes. The variable ROUNDED is the size rounded up to whatever alignment
+ the caller wants.
+
+ Use the expression `assemble_name (STREAM, NAME)' to output the name itself;
+ before and after that, output the additional assembler syntax for defining
+ the name, and a newline.
+
+ This macro controls how the assembler definitions of uninitialized static
+ variables are output. */
+/* #define ASM_OUTPUT_LOCAL(STREAM, NAME, SIZE, ROUNDED) */
+
+/* Like `ASM_OUTPUT_LOCAL' except takes the required alignment as a separate,
+ explicit argument. If you define this macro, it is used in place of
+ `ASM_OUTPUT_LOCAL', and gives you more flexibility in handling the required
+ alignment of the variable. The alignment is specified as the number of
+ bits.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_ALIGNED_LOCAL(STREAM, NAME, SIZE, ALIGNMENT) */
+
+/* Like `ASM_OUTPUT_ALIGNED_LOCAL' except that it takes an additional
+ parameter - the DECL of variable to be output, if there is one.
+ This macro can be called with DECL == NULL_TREE. If you define
+ this macro, it is used in place of `ASM_OUTPUT_LOCAL' and
+ `ASM_OUTPUT_ALIGNED_LOCAL', and gives you more flexibility in
+ handling the destination of the variable. */
+/* #define ASM_OUTPUT_DECL_LOCAL(STREAM, DECL, NAME, SIZE, ALIGNMENT) */
+
+/* If defined, it is similar to `ASM_OUTPUT_LOCAL', except that it is used when
+ NAME is shared. If not defined, `ASM_OUTPUT_LOCAL' will be used. */
+/* #define ASM_OUTPUT_SHARED_LOCAL (STREAM, NAME, SIZE, ROUNDED) */
+
+/*}}}*/ \f
+/*{{{ Output and Generation of Labels. */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM the
+ assembler definition of a label named NAME. Use the expression
+ `assemble_name (STREAM, NAME)' to output the name itself; before and after
+ that, output the additional assembler syntax for defining the name, and a
+ newline. */
+#define ASM_OUTPUT_LABEL(STREAM, NAME) \
+do { \
+ assemble_name (STREAM, NAME); \
+ fputs (":\n", STREAM); \
+} while (0)
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM any text
+ necessary for declaring the name NAME of a function which is being defined.
+ This macro is responsible for outputting the label definition (perhaps using
+ `ASM_OUTPUT_LABEL'). The argument DECL is the `FUNCTION_DECL' tree node
+ representing the function.
+
+ If this macro is not defined, then the function name is defined in the usual
+ manner as a label (by means of `ASM_OUTPUT_LABEL').
+
+ Defined in svr4.h. */
+/* #define ASM_DECLARE_FUNCTION_NAME(STREAM, NAME, DECL) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM any text
+ necessary for declaring the size of a function which is being defined. The
+ argument NAME is the name of the function. The argument DECL is the
+ `FUNCTION_DECL' tree node representing the function.
+
+ If this macro is not defined, then the function size is not defined.
+
+ Defined in svr4.h. */
+/* #define ASM_DECLARE_FUNCTION_SIZE(STREAM, NAME, DECL) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM any text
+ necessary for declaring the name NAME of an initialized variable which is
+ being defined. This macro must output the label definition (perhaps using
+ `ASM_OUTPUT_LABEL'). The argument DECL is the `VAR_DECL' tree node
+ representing the variable.
+
+ If this macro is not defined, then the variable name is defined in the usual
+ manner as a label (by means of `ASM_OUTPUT_LABEL').
+
+ Defined in svr4.h. */
+/* #define ASM_DECLARE_OBJECT_NAME(STREAM, NAME, DECL) */
+
+/* A C statement (sans semicolon) to finish up declaring a variable name once
+ the compiler has processed its initializer fully and thus has had a chance
+ to determine the size of an array when controlled by an initializer. This
+ is used on systems where it's necessary to declare something about the size
+ of the object.
+
+ If you don't define this macro, that is equivalent to defining it to do
+ nothing.
+
+ Defined in svr4.h. */
+/* #define ASM_FINISH_DECLARE_OBJECT(STREAM, DECL, TOPLEVEL, ATEND) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM some
+ commands that will make the label NAME global; that is, available for
+ reference from other files. Use the expression `assemble_name (STREAM,
+ NAME)' to output the name itself; before and after that, output the
+ additional assembler syntax for making that name global, and a newline. */
+#define ASM_GLOBALIZE_LABEL(STREAM,NAME) \
+do { \
+ fputs ("\t.globl ", STREAM); \
+ assemble_name (STREAM, NAME); \
+ fputs ("\n", STREAM); \
+} while (0)
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM some
+ commands that will make the label NAME weak; that is, available for
+ reference from other files but only used if no other definition is
+ available. Use the expression `assemble_name (STREAM, NAME)' to output the
+ name itself; before and after that, output the additional assembler syntax
+ for making that name weak, and a newline.
+
+ If you don't define this macro, GNU CC will not support weak symbols and you
+ should not define the `SUPPORTS_WEAK' macro.
+
+ Defined in svr4.h. */
+/* #define ASM_WEAKEN_LABEL */
+
+/* A C expression which evaluates to true if the target supports weak symbols.
+
+ If you don't define this macro, `defaults.h' provides a default definition.
+ If `ASM_WEAKEN_LABEL' is defined, the default definition is `1'; otherwise,
+ it is `0'. Define this macro if you want to control weak symbol support
+ with a compiler flag such as `-melf'. */
+/* #define SUPPORTS_WEAK */
+
+/* A C statement (sans semicolon) to mark DECL to be emitted as a
+ public symbol such that extra copies in multiple translation units
+ will be discarded by the linker. Define this macro if your object
+ file format provides support for this concept, such as the `COMDAT'
+ section flags in the Microsoft Windows PE/COFF format, and this
+ support requires changes to DECL, such as putting it in a separate
+ section.
+
+ Defined in svr4.h. */
+/* #define MAKE_DECL_ONE_ONLY */
+
+/* A C expression which evaluates to true if the target supports one-only
+ semantics.
+
+ If you don't define this macro, `varasm.c' provides a default definition.
+ If `MAKE_DECL_ONE_ONLY' is defined, the default definition is `1';
+ otherwise, it is `0'. Define this macro if you want to control one-only
+ symbol support with a compiler flag, or if setting the `DECL_ONE_ONLY' flag
+ is enough to mark a declaration to be emitted as one-only. */
+/* #define SUPPORTS_ONE_ONLY */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM any text
+ necessary for declaring the name of an external symbol named NAME which is
+ referenced in this compilation but not defined. The value of DECL is the
+ tree node for the declaration.
+
+ This macro need not be defined if it does not need to output anything. The
+ GNU assembler and most Unix assemblers don't require anything. */
+/* #define ASM_OUTPUT_EXTERNAL(STREAM, DECL, NAME) */
+
+/* A C statement (sans semicolon) to output on STREAM an assembler pseudo-op to
+ declare a library function name external. The name of the library function
+ is given by SYMREF, which has type `rtx' and is a `symbol_ref'.
+
+ This macro need not be defined if it does not need to output anything. The
+ GNU assembler and most Unix assemblers don't require anything.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_EXTERNAL_LIBCALL(STREAM, SYMREF) */
+
+/* A C statement (sans semicolon) to output to the stdio stream STREAM a
+ reference in assembler syntax to a label named NAME. This should add `_' to
+ the front of the name, if that is customary on your operating system, as it
+ is in most Berkeley Unix systems. This macro is used in `assemble_name'. */
+/* #define ASM_OUTPUT_LABELREF(STREAM, NAME) */
+
+/* A C statement to output to the stdio stream STREAM a label whose name is
+ made from the string PREFIX and the number NUM.
+
+ It is absolutely essential that these labels be distinct from the labels
+ used for user-level functions and variables. Otherwise, certain programs
+ will have name conflicts with internal labels.
+
+ It is desirable to exclude internal labels from the symbol table of the
+ object file. Most assemblers have a naming convention for labels that
+ should be excluded; on many systems, the letter `L' at the beginning of a
+ label has this effect. You should find out what convention your system
+ uses, and follow it.
+
+ The usual definition of this macro is as follows:
+
+ fprintf (STREAM, "L%s%d:\n", PREFIX, NUM)
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_INTERNAL_LABEL(STREAM, PREFIX, NUM) */
+
+/* A C expression to assign to OUTVAR (which is a variable of type `char *') a
+ newly allocated string made from the string NAME and the number NUMBER, with
+ some suitable punctuation added. Use `alloca' to get space for the string.
+
+ The string will be used as an argument to `ASM_OUTPUT_LABELREF' to produce
+ an assembler label for an internal static variable whose name is NAME.
+ Therefore, the string must be such as to result in valid assembler code.
+ The argument NUMBER is different each time this macro is executed; it
+ prevents conflicts between similarly-named internal static variables in
+ different scopes.
+
+ Ideally this string should not be a valid C identifier, to prevent any
+ conflict with the user's own symbols. Most assemblers allow periods or
+ percent signs in assembler symbols; putting at least one of these between
+ the name and the number will suffice. */
+#define ASM_FORMAT_PRIVATE_NAME(OUTVAR, NAME, NUMBER) \
+do { \
+ (OUTVAR) = (char *) alloca (strlen ((NAME)) + 12); \
+ sprintf ((OUTVAR), "%s.%ld", (NAME), (long)(NUMBER)); \
+} while (0)
+
+/* A C statement to output to the stdio stream STREAM assembler code which
+ defines (equates) the symbol NAME to have the value VALUE.
+
+ If SET_ASM_OP is defined, a default definition is provided which is correct
+ for most systems.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_DEF(STREAM, NAME, VALUE) */
+
+/* A C statement to output to the stdio stream STREAM assembler code which
+ defines (equates) the weak symbol NAME to have the value VALUE.
+
+ Define this macro if the target only supports weak aliases; define
+ ASM_OUTPUT_DEF instead if possible. */
+/* #define ASM_OUTPUT_WEAK_ALIAS (STREAM, NAME, VALUE) */
+
+/* Define this macro to override the default assembler names used for Objective
+ C methods.
+
+ The default name is a unique method number followed by the name of the class
+ (e.g. `_1_Foo'). For methods in categories, the name of the category is
+ also included in the assembler name (e.g. `_1_Foo_Bar').
+
+ These names are safe on most systems, but make debugging difficult since the
+ method's selector is not present in the name. Therefore, particular systems
+ define other ways of computing names.
+
+ BUF is an expression of type `char *' which gives you a buffer in which to
+ store the name; its length is as long as CLASS_NAME, CAT_NAME and SEL_NAME
+ put together, plus 50 characters extra.
+
+ The argument IS_INST specifies whether the method is an instance method or a
+ class method; CLASS_NAME is the name of the class; CAT_NAME is the name of
+ the category (or NULL if the method is not in a category); and SEL_NAME is
+ the name of the selector.
+
+ On systems where the assembler can handle quoted names, you can use this
+ macro to provide more human-readable names. */
+/* #define OBJC_GEN_METHOD_LABEL(BUF, IS_INST, CLASS_NAME, CAT_NAME, SEL_NAME) */
+
+/*}}}*/ \f
+/*{{{ Macros Controlling Initialization Routines. */
+
+/* If defined, a C string constant for the assembler operation to identify the
+ following data as initialization code. If not defined, GNU CC will assume
+ such a section does not exist. When you are using special sections for
+ initialization and termination functions, this macro also controls how
+ `crtstuff.c' and `libgcc2.c' arrange to run the initialization functions.
+
+ Defined in svr4.h. */
+/* #define INIT_SECTION_ASM_OP */
+
+/* If defined, `main' will not call `__main' as described above. This macro
+ should be defined for systems that control the contents of the init section
+ on a symbol-by-symbol basis, such as OSF/1, and should not be defined
+ explicitly for systems that support `INIT_SECTION_ASM_OP'. */
+/* #define HAS_INIT_SECTION */
+
+/* If defined, a C string constant for a switch that tells the linker that the
+ following symbol is an initialization routine. */
+/* #define LD_INIT_SWITCH */
+
+/* If defined, a C string constant for a switch that tells the linker that the
+ following symbol is a finalization routine. */
+/* #define LD_FINI_SWITCH */
+
+/* If defined, `main' will call `__main' despite the presence of
+ `INIT_SECTION_ASM_OP'. This macro should be defined for systems where the
+ init section is not actually run automatically, but is still useful for
+ collecting the lists of constructors and destructors. */
+/* #define INVOKE__main */
+
+/* Define this macro as a C statement to output on the stream STREAM the
+ assembler code to arrange to call the function named NAME at initialization
+ time.
+
+ Assume that NAME is the name of a C function generated automatically by the
+ compiler. This function takes no arguments. Use the function
+ `assemble_name' to output the name NAME; this performs any system-specific
+ syntactic transformations such as adding an underscore.
+
+ If you don't define this macro, nothing special is output to arrange to call
+ the function. This is correct when the function will be called in some
+ other manner--for example, by means of the `collect2' program, which looks
+ through the symbol table to find these functions by their names.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_CONSTRUCTOR(STREAM, NAME) */
+
+/* This is like `ASM_OUTPUT_CONSTRUCTOR' but used for termination functions
+ rather than initialization functions.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_DESTRUCTOR(STREAM, NAME) */
+
+/* If your system uses `collect2' as the means of processing constructors, then
+ that program normally uses `nm' to scan an object file for constructor
+ functions to be called. On certain kinds of systems, you can define these
+ macros to make `collect2' work faster (and, in some cases, make it work at
+ all): */
+
+/* Define this macro if the system uses COFF (Common Object File Format) object
+ files, so that `collect2' can assume this format and scan object files
+ directly for dynamic constructor/destructor functions. */
+/* #define OBJECT_FORMAT_COFF */
+
+/* Define this macro if the system uses ROSE format object files, so that
+ `collect2' can assume this format and scan object files directly for dynamic
+ constructor/destructor functions.
+
+ These macros are effective only in a native compiler; `collect2' as
+ part of a cross compiler always uses `nm' for the target machine. */
+/* #define OBJECT_FORMAT_ROSE */
+
+/* Define this macro if the system uses ELF format object files.
+
+ Defined in svr4.h. */
+/* #define OBJECT_FORMAT_ELF */
+
+/* Define this macro as a C string constant containing the file name to use to
+ execute `nm'. The default is to search the path normally for `nm'.
+
+ If your system supports shared libraries and has a program to list the
+ dynamic dependencies of a given library or executable, you can define these
+ macros to enable support for running initialization and termination
+ functions in shared libraries: */
+/* #define REAL_NM_FILE_NAME */
+
+/* Define this macro to a C string constant containing the name of the program
+ which lists dynamic dependencies, like `"ldd"' under SunOS 4. */
+/* #define LDD_SUFFIX */
+
+/* Define this macro to be C code that extracts filenames from the output of
+ the program denoted by `LDD_SUFFIX'. PTR is a variable of type `char *'
+ that points to the beginning of a line of output from `LDD_SUFFIX'. If the
+ line lists a dynamic dependency, the code must advance PTR to the beginning
+ of the filename on that line. Otherwise, it must set PTR to `NULL'. */
+/* #define PARSE_LDD_OUTPUT (PTR) */
+
+/*}}}*/ \f
+/*{{{ Output of Assembler Instructions. */
+
+/* Define this macro if you are using an unusual assembler that requires
+ different names for the machine instructions.
+
+ The definition is a C statement or statements which output an assembler
+ instruction opcode to the stdio stream STREAM. The macro-operand PTR is a
+ variable of type `char *' which points to the opcode name in its "internal"
+ form--the form that is written in the machine description. The definition
+ should output the opcode name to STREAM, performing any translation you
+ desire, and increment the variable PTR to point at the end of the opcode so
+ that it will not be output twice.
+
+ In fact, your macro definition may process less than the entire opcode name,
+ or more than the opcode name; but if you want to process text that includes
+ `%'-sequences to substitute operands, you must take care of the substitution
+ yourself. Just be sure to increment PTR over whatever text should not be
+ output normally.
+
+ If you need to look at the operand values, they can be found as the elements
+ of `recog_data.operand'.
+
+ If the macro definition does nothing, the instruction is output in the usual
+ way. */
+/* #define ASM_OUTPUT_OPCODE(STREAM, PTR) */
+
+/* If defined, a C statement to be executed just prior to the output of
+ assembler code for INSN, to modify the extracted operands so they will be
+ output differently.
+
+ Here the argument OPVEC is the vector containing the operands extracted from
+ INSN, and NOPERANDS is the number of elements of the vector which contain
+ meaningful data for this insn. The contents of this vector are what will be
+ used to convert the insn template into assembler code, so you can change the
+ assembler output by changing the contents of the vector.
+
+ This macro is useful when various assembler syntaxes share a single file of
+ instruction patterns; by defining this macro differently, you can cause a
+ large class of instructions to be output differently (such as with
+ rearranged operands). Naturally, variations in assembler syntax affecting
+ individual insn patterns ought to be handled by writing conditional output
+ routines in those patterns.
+
+ If this macro is not defined, it is equivalent to a null statement. */
+/* #define FINAL_PRESCAN_INSN(INSN, OPVEC, NOPERANDS) */
+
+/* If defined, `FINAL_PRESCAN_INSN' will be called on each
+ `CODE_LABEL'. In that case, OPVEC will be a null pointer and
+ NOPERANDS will be zero. */
+/* #define FINAL_PRESCAN_LABEL */
+
+/* A C compound statement to output to stdio stream STREAM the assembler syntax
+ for an instruction operand X. X is an RTL expression.
+
+ CODE is a value that can be used to specify one of several ways of printing
+ the operand. It is used when identical operands must be printed differently
+ depending on the context. CODE comes from the `%' specification that was
+ used to request printing of the operand. If the specification was just
+ `%DIGIT' then CODE is 0; if the specification was `%LTR DIGIT' then CODE is
+ the ASCII code for LTR.
+
+ If X is a register, this macro should print the register's name. The names
+ can be found in an array `reg_names' whose type is `char *[]'. `reg_names'
+ is initialized from `REGISTER_NAMES'.
+
+ When the machine description has a specification `%PUNCT' (a `%' followed by
+ a punctuation character), this macro is called with a null pointer for X and
+ the punctuation character for CODE. */
+#define PRINT_OPERAND(STREAM, X, CODE) fr30_print_operand (STREAM, X, CODE)
+
+extern void fr30_print_operand STDIO_PROTO((FILE *, Rtx, int));
+
+/* A C expression which evaluates to true if CODE is a valid punctuation
+ character for use in the `PRINT_OPERAND' macro. If
+ `PRINT_OPERAND_PUNCT_VALID_P' is not defined, it means that no punctuation
+ characters (except for the standard one, `%') are used in this way. */
+#define PRINT_OPERAND_PUNCT_VALID_P(CODE) (CODE == '#')
+
+/* A C compound statement to output to stdio stream STREAM the assembler syntax
+ for an instruction operand that is a memory reference whose address is X. X
+ is an RTL expression.
+
+ On some machines, the syntax for a symbolic address depends on the section
+ that the address refers to. On these machines, define the macro
+ `ENCODE_SECTION_INFO' to store the information into the `symbol_ref', and
+ then check for it here. *Note Assembler Format::. */
+#define PRINT_OPERAND_ADDRESS(STREAM, X) fr30_print_operand_address (STREAM, X)
+extern void fr30_print_operand_address STDIO_PROTO((FILE *, Rtx));
+
+/* A C statement, to be executed after all slot-filler instructions have been
+ output. If necessary, call `dbr_sequence_length' to determine the number of
+ slots filled in a sequence (zero if not currently outputting a sequence), to
+ decide how many no-ops to output, or whatever.
+
+ Don't define this macro if it has nothing to do, but it is helpful in
+ reading assembly output if the extent of the delay sequence is made explicit
+ (e.g. with white space).
+
+ Note that output routines for instructions with delay slots must be prepared
+ to deal with not being output as part of a sequence (i.e. when the
+ scheduling pass is not run, or when no slot fillers could be found.) The
+ variable `final_sequence' is null when not processing a sequence, otherwise
+ it contains the `sequence' rtx being output. */
+/* #define DBR_OUTPUT_SEQEND(FILE) */
+
+/* If defined, C string expressions to be used for the `%R', `%L', `%U', and
+ `%I' options of `asm_fprintf' (see `final.c'). These are useful when a
+ single `md' file must support multiple assembler formats. In that case, the
+ various `tm.h' files can define these macros differently.
+
+ USER_LABEL_PREFIX is defined in svr4.h. */
+#define REGISTER_PREFIX "%"
+#define LOCAL_LABEL_PREFIX "."
+#define USER_LABEL_PREFIX ""
+#define IMMEDIATE_PREFIX ""
+
+/* If your target supports multiple dialects of assembler language (such as
+ different opcodes), define this macro as a C expression that gives the
+ numeric index of the assembler language dialect to use, with zero as the
+ first variant.
+
+ If this macro is defined, you may use `{option0|option1|option2...}'
+ constructs in the output templates of patterns or
+ in the first argument of `asm_fprintf'. This construct outputs `option0',
+ `option1' or `option2', etc., if the value of `ASSEMBLER_DIALECT' is zero,
+ one or two, etc. Any special characters within these strings retain their
+ usual meaning.
+
+ If you do not define this macro, the characters `{', `|' and `}' do not have
+ any special meaning when used in templates or operands to `asm_fprintf'.
+
+ Define the macros `REGISTER_PREFIX', `LOCAL_LABEL_PREFIX',
+ `USER_LABEL_PREFIX' and `IMMEDIATE_PREFIX' if you can express the variations
+ in assemble language syntax with that mechanism. Define `ASSEMBLER_DIALECT'
+ and use the `{option0|option1}' syntax if the syntax variant are larger and
+ involve such things as different opcodes or operand order. */
+/* #define ASSEMBLER_DIALECT */
+
+/* A C expression to output to STREAM some assembler code which will push hard
+ register number REGNO onto the stack. The code need not be optimal, since
+ this macro is used only when profiling. */
+/* #define ASM_OUTPUT_REG_PUSH (STREAM, REGNO) */
+
+/* A C expression to output to STREAM some assembler code which will pop hard
+ register number REGNO off of the stack. The code need not be optimal, since
+ this macro is used only when profiling. */
+/* #define ASM_OUTPUT_REG_POP (STREAM, REGNO) */
+
+/*}}}*/ \f
+/*{{{ Output of dispatch tables. */
+
+/* This macro should be provided on machines where the addresses in a dispatch
+ table are relative to the table's own address.
+
+ The definition should be a C statement to output to the stdio stream STREAM
+ an assembler pseudo-instruction to generate a difference between two labels.
+ VALUE and REL are the numbers of two internal labels. The definitions of
+ these labels are output using `ASM_OUTPUT_INTERNAL_LABEL', and they must be
+ printed in the same way here. For example,
+
+ fprintf (STREAM, "\t.word L%d-L%d\n", VALUE, REL) */
+#define ASM_OUTPUT_ADDR_DIFF_ELT(STREAM, BODY, VALUE, REL) \
+fprintf (STREAM, "\t.word .L%d-.L%d\n", VALUE, REL)
+
+/* This macro should be provided on machines where the addresses in a dispatch
+ table are absolute.
+
+ The definition should be a C statement to output to the stdio stream STREAM
+ an assembler pseudo-instruction to generate a reference to a label. VALUE
+ is the number of an internal label whose definition is output using
+ `ASM_OUTPUT_INTERNAL_LABEL'. For example,
+
+ fprintf (STREAM, "\t.word L%d\n", VALUE) */
+#define ASM_OUTPUT_ADDR_VEC_ELT(STREAM, VALUE) \
+fprintf (STREAM, "\t.word .L%d\n", VALUE)
+
+/* Define this if the label before a jump-table needs to be output specially.
+ The first three arguments are the same as for `ASM_OUTPUT_INTERNAL_LABEL';
+ the fourth argument is the jump-table which follows (a `jump_insn'
+ containing an `addr_vec' or `addr_diff_vec').
+
+ This feature is used on system V to output a `swbeg' statement for the
+ table.
+
+ If this macro is not defined, these labels are output with
+ `ASM_OUTPUT_INTERNAL_LABEL'.
+
+ Defined in svr4.h. */
+/* #define ASM_OUTPUT_CASE_LABEL(STREAM, PREFIX, NUM, TABLE) */
+
+/* Define this if something special must be output at the end of a jump-table.
+ The definition should be a C statement to be executed after the assembler
+ code for the table is written. It should write the appropriate code to
+ stdio stream STREAM. The argument TABLE is the jump-table insn, and NUM is
+ the label-number of the preceding label.
+
+ If this macro is not defined, nothing special is output at the end of the
+ jump-table. */
+/* #define ASM_OUTPUT_CASE_END(STREAM, NUM, TABLE) */
+
+/*}}}*/ \f
+/*{{{ Assembler Commands for Exception Regions. */
+
+/* A C expression to output text to mark the start of an exception region.
+
+ This macro need not be defined on most platforms. */
+/* #define ASM_OUTPUT_EH_REGION_BEG() */
+
+/* A C expression to output text to mark the end of an exception region.
+
+ This macro need not be defined on most platforms. */
+/* #define ASM_OUTPUT_EH_REGION_END() */
+
+/* A C expression to switch to the section in which the main exception table is
+ to be placed. The default is a section named
+ `.gcc_except_table' on machines that support named sections via
+ `ASM_OUTPUT_SECTION_NAME', otherwise if `-fpic' or `-fPIC' is in effect, the
+ `data_section', otherwise the `readonly_data_section'. */
+/* #define EXCEPTION_SECTION() */
+
+/* If defined, a C string constant for the assembler operation to switch to the
+ section for exception handling frame unwind information. If not defined,
+ GNU CC will provide a default definition if the target supports named
+ sections. `crtstuff.c' uses this macro to switch to the appropriate
+ section.
+
+ You should define this symbol if your target supports DWARF 2 frame unwind
+ information and the default definition does not work. */
+/* #define EH_FRAME_SECTION_ASM_OP */
+
+/* A C expression that is nonzero if the normal exception table output should
+ be omitted.
+
+ This macro need not be defined on most platforms. */
+/* #define OMIT_EH_TABLE() */
+
+/* Alternate runtime support for looking up an exception at runtime and finding
+ the associated handler, if the default method won't work.
+
+ This macro need not be defined on most platforms. */
+/* #define EH_TABLE_LOOKUP() */
+
+/* A C expression that decides whether or not the current function needs to
+ have a function unwinder generated for it. See the file `except.c' for
+ details on when to define this, and how. */
+/* #define DOESNT_NEED_UNWINDER */
+
+/* An rtx used to mask the return address found via RETURN_ADDR_RTX, so that it
+ does not contain any extraneous set bits in it. */
+/* #define MASK_RETURN_ADDR */
+
+/* Define this macro to 0 if your target supports DWARF 2 frame unwind
+ information, but it does not yet work with exception handling. Otherwise,
+ if your target supports this information (if it defines
+ `INCOMING_RETURN_ADDR_RTX' and either `UNALIGNED_INT_ASM_OP' or
+ `OBJECT_FORMAT_ELF'), GCC will provide a default definition of 1.
+
+ If this macro is defined to 1, the DWARF 2 unwinder will be the default
+ exception handling mechanism; otherwise, setjmp/longjmp will be used by
+ default.
+
+ If this macro is defined to anything, the DWARF 2 unwinder will be used
+ instead of inline unwinders and __unwind_function in the non-setjmp case. */
+/* #define DWARF2_UNWIND_INFO */
+
+/*}}}*/ \f
+/*{{{ Assembler Commands for Alignment. */
+
+/* The alignment (log base 2) to put in front of LABEL, which follows
+ a BARRIER.
+
+ This macro need not be defined if you don't want any special alignment to be
+ done at such a time. Most machine descriptions do not currently define the
+ macro. */
+/* #define LABEL_ALIGN_AFTER_BARRIER(LABEL) */
+
+/* The desired alignment for the location counter at the beginning
+ of a loop.
+
+ This macro need not be defined if you don't want any special alignment to be
+ done at such a time. Most machine descriptions do not currently define the
+ macro. */
+/* #define LOOP_ALIGN(LABEL) */
+
+/* Define this macro if `ASM_OUTPUT_SKIP' should not be used in the text
+ section because it fails put zeros in the bytes that are skipped. This is
+ true on many Unix systems, where the pseudo-op to skip bytes produces no-op
+ instructions rather than zeros when used in the text section. */
+/* #define ASM_NO_SKIP_IN_TEXT */
+
+/* A C statement to output to the stdio stream STREAM an assembler command to
+ advance the location counter to a multiple of 2 to the POWER bytes. POWER
+ will be a C expression of type `int'. */
+#define ASM_OUTPUT_ALIGN(STREAM, POWER) \
+ fprintf ((STREAM), "\t.p2align %d\n", (POWER))
+
+/*}}}*/ \f
+/*{{{ Macros Affecting all Debug Formats. */
+
+/* A C expression that returns the DBX register number for the compiler
+ register number REGNO. In simple cases, the value of this expression may be
+ REGNO itself. But sometimes there are some registers that the compiler
+ knows about and DBX does not, or vice versa. In such cases, some register
+ may need to have one number in the compiler and another for DBX.
+
+ If two registers have consecutive numbers inside GNU CC, and they can be
+ used as a pair to hold a multiword value, then they *must* have consecutive
+ numbers after renumbering with `DBX_REGISTER_NUMBER'. Otherwise, debuggers
+ will be unable to access such a pair, because they expect register pairs to
+ be consecutive in their own numbering scheme.
+
+ If you find yourself defining `DBX_REGISTER_NUMBER' in way that does not
+ preserve register pairs, then what you must do instead is redefine the
+ actual register numbering scheme. */
+#define DBX_REGISTER_NUMBER(REGNO) (REGNO)
+
+/* A C expression that returns the integer offset value for an automatic
+ variable having address X (an RTL expression). The default computation
+ assumes that X is based on the frame-pointer and gives the offset from the
+ frame-pointer. This is required for targets that produce debugging output
+ for DBX or COFF-style debugging output for SDB and allow the frame-pointer
+ to be eliminated when the `-g' options is used. */
+/* #define DEBUGGER_AUTO_OFFSET(X) */
+
+/* A C expression that returns the integer offset value for an argument having
+ address X (an RTL expression). The nominal offset is OFFSET. */
+/* #define DEBUGGER_ARG_OFFSET(OFFSET, X) */
+
+/* A C expression that returns the type of debugging output GNU CC produces
+ when the user specifies `-g' or `-ggdb'. Define this if you have arranged
+ for GNU CC to support more than one format of debugging output. Currently,
+ the allowable values are `DBX_DEBUG', `SDB_DEBUG', `DWARF_DEBUG',
+ `DWARF2_DEBUG', and `XCOFF_DEBUG'.
+
+ The value of this macro only affects the default debugging output; the user
+ can always get a specific type of output by using `-gstabs', `-gcoff',
+ `-gdwarf-1', `-gdwarf-2', or `-gxcoff'.
+
+ Defined in svr4.h. */
+#undef PREFERRED_DEBUGGING_TYPE
+#define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG
+
+/*}}}*/ \f
+/*{{{ Macros for SDB and Dwarf Output. */
+
+/* Define this macro if GNU CC should produce dwarf format debugging output in
+ response to the `-g' option.
+
+ Defined in svr4.h. */
+#define DWARF_DEBUGGING_INFO
+
+/* Define this macro if GNU CC should produce dwarf version 2 format debugging
+ output in response to the `-g' option.
+
+ To support optional call frame debugging information, you must also define
+ `INCOMING_RETURN_ADDR_RTX' and either set `RTX_FRAME_RELATED_P' on the
+ prologue insns if you use RTL for the prologue, or call `dwarf2out_def_cfa'
+ and `dwarf2out_reg_save' as appropriate from `FUNCTION_PROLOGUE' if you
+ don't.
+
+ Defined in svr4.h. */
+#define DWARF2_DEBUGGING_INFO
+
+/* Define these macros to override the assembler syntax for the special SDB
+ assembler directives. See `sdbout.c' for a list of these macros and their
+ arguments. If the standard syntax is used, you need not define them
+ yourself. */
+/* #define PUT_SDB_... */
+
+/* Some assemblers do not support a semicolon as a delimiter, even between SDB
+ assembler directives. In that case, define this macro to be the delimiter
+ to use (usually `\n'). It is not necessary to define a new set of
+ `PUT_SDB_OP' macros if this is the only change required. */
+/* #define SDB_DELIM */
+
+/* Define this macro to override the usual method of constructing a dummy name
+ for anonymous structure and union types. See `sdbout.c' for more
+ information. */
+/* #define SDB_GENERATE_FAKE */
+
+/* Define this macro to allow references to unknown structure, union, or
+ enumeration tags to be emitted. Standard COFF does not allow handling of
+ unknown references, MIPS ECOFF has support for it. */
+/* #define SDB_ALLOW_UNKNOWN_REFERENCES */
+
+/* Define this macro to allow references to structure, union, or enumeration
+ tags that have not yet been seen to be handled. Some assemblers choke if
+ forward tags are used, while some require it. */
+/* #define SDB_ALLOW_FORWARD_REFERENCES */
+
+#define DWARF_LINE_MIN_INSTR_LENGTH 2
+
+/*}}}*/ \f
+/*{{{ Cross Compilation and Floating Point. */
+
+/* While all modern machines use 2's complement representation for integers,
+ there are a variety of representations for floating point numbers. This
+ means that in a cross-compiler the representation of floating point numbers
+ in the compiled program may be different from that used in the machine doing
+ the compilation.
+
+ Because different representation systems may offer different amounts of
+ range and precision, the cross compiler cannot safely use the host machine's
+ floating point arithmetic. Therefore, floating point constants must be
+ represented in the target machine's format. This means that the cross
+ compiler cannot use `atof' to parse a floating point constant; it must have
+ its own special routine to use instead. Also, constant folding must emulate
+ the target machine's arithmetic (or must not be done at all).
+
+ The macros in the following table should be defined only if you are cross
+ compiling between different floating point formats.
+
+ Otherwise, don't define them. Then default definitions will be set up which
+ use `double' as the data type, `==' to test for equality, etc.
+
+ You don't need to worry about how many times you use an operand of any of
+ these macros. The compiler never uses operands which have side effects. */
+
+/* A macro for the C data type to be used to hold a floating point value in the
+ target machine's format. Typically this would be a `struct' containing an
+ array of `int'. */
+/* #define REAL_VALUE_TYPE */
+
+/* A macro for a C expression which compares for equality the two values, X and
+ Y, both of type `REAL_VALUE_TYPE'. */
+/* #define REAL_VALUES_EQUAL(X, Y) */
+
+/* A macro for a C expression which tests whether X is less than Y, both values
+ being of type `REAL_VALUE_TYPE' and interpreted as floating point numbers in
+ the target machine's representation. */
+/* #define REAL_VALUES_LESS(X, Y) */
+
+/* A macro for a C expression which performs the standard library function
+ `ldexp', but using the target machine's floating point representation. Both
+ X and the value of the expression have type `REAL_VALUE_TYPE'. The second
+ argument, SCALE, is an integer. */
+/* #define REAL_VALUE_LDEXP(X, SCALE) */
+
+/* A macro whose definition is a C expression to convert the target-machine
+ floating point value X to a signed integer. X has type `REAL_VALUE_TYPE'. */
+/* #define REAL_VALUE_FIX(X) */
+
+/* A macro whose definition is a C expression to convert the target-machine
+ floating point value X to an unsigned integer. X has type
+ `REAL_VALUE_TYPE'. */
+/* #define REAL_VALUE_UNSIGNED_FIX(X) */
+
+/* A macro whose definition is a C expression to round the target-machine
+ floating point value X towards zero to an integer value (but still as a
+ floating point number). X has type `REAL_VALUE_TYPE', and so does the
+ value. */
+/* #define REAL_VALUE_RNDZINT(X) */
+
+/* A macro whose definition is a C expression to round the target-machine
+ floating point value X towards zero to an unsigned integer value (but still
+ represented as a floating point number). X has type `REAL_VALUE_TYPE', and
+ so does the value. */
+/* #define REAL_VALUE_UNSIGNED_RNDZINT(X) */
+
+/* A macro for a C expression which converts STRING, an expression of type
+ `char *', into a floating point number in the target machine's
+ representation for mode MODE. The value has type `REAL_VALUE_TYPE'. */
+/* #define REAL_VALUE_ATOF(STRING, MODE) */
+
+/* Define this macro if infinity is a possible floating point value, and
+ therefore division by 0 is legitimate. */
+/* #define REAL_INFINITY */
+
+/* A macro for a C expression which determines whether X, a floating point
+ value, is infinity. The value has type `int'. By default, this is defined
+ to call `isinf'. */
+/* #define REAL_VALUE_ISINF(X) */
+
+/* A macro for a C expression which determines whether X, a floating point
+ value, is a "nan" (not-a-number). The value has type `int'. By default,
+ this is defined to call `isnan'. */
+/* #define REAL_VALUE_ISNAN(X) */
+
+/* Define the following additional macros if you want to make floating point
+ constant folding work while cross compiling. If you don't define them,
+ cross compilation is still possible, but constant folding will not happen
+ for floating point values. */
+
+/* A macro for a C statement which calculates an arithmetic operation of the
+ two floating point values X and Y, both of type `REAL_VALUE_TYPE' in the
+ target machine's representation, to produce a result of the same type and
+ representation which is stored in OUTPUT (which will be a variable).
+
+ The operation to be performed is specified by CODE, a tree code which will
+ always be one of the following: `PLUS_EXPR', `MINUS_EXPR', `MULT_EXPR',
+ `RDIV_EXPR', `MAX_EXPR', `MIN_EXPR'.
+
+ The expansion of this macro is responsible for checking for overflow. If
+ overflow happens, the macro expansion should execute the statement `return
+ 0;', which indicates the inability to perform the arithmetic operation
+ requested. */
+/* #define REAL_ARITHMETIC(OUTPUT, CODE, X, Y) */
+
+/* A macro for a C expression which returns the negative of the floating point
+ value X. Both X and the value of the expression have type `REAL_VALUE_TYPE'
+ and are in the target machine's floating point representation.
+
+ There is no way for this macro to report overflow, since overflow can't
+ happen in the negation operation. */
+/* #define REAL_VALUE_NEGATE(X) */
+
+/* A macro for a C expression which converts the floating point value X to mode
+ MODE.
+
+ Both X and the value of the expression are in the target machine's floating
+ point representation and have type `REAL_VALUE_TYPE'. However, the value
+ should have an appropriate bit pattern to be output properly as a floating
+ constant whose precision accords with mode MODE.
+
+ There is no way for this macro to report overflow. */
+/* #define REAL_VALUE_TRUNCATE(MODE, X) */
+
+/* A macro for a C expression which converts a floating point value X into a
+ double-precision integer which is then stored into LOW and HIGH, two
+ variables of type INT. */
+/* #define REAL_VALUE_TO_INT(LOW, HIGH, X) */
+
+/* A macro for a C expression which converts a double-precision integer found
+ in LOW and HIGH, two variables of type INT, into a floating point value
+ which is then stored into X. */
+/* #define REAL_VALUE_FROM_INT(X, LOW, HIGH) */
+
+/*}}}*/ \f
+/*{{{ Miscellaneous Parameters. */
+
+/* An alias for a machine mode name. This is the machine mode that elements of
+ a jump-table should have. */
+#define CASE_VECTOR_MODE SImode
+
+/* Define as C expression which evaluates to nonzero if the tablejump
+ instruction expects the table to contain offsets from the address of the
+ table.
+ Do not define this if the table should contain absolute addresses. */
+/* #define CASE_VECTOR_PC_RELATIVE 1 */
+
+/* Define this if control falls through a `case' insn when the index value is
+ out of range. This means the specified default-label is actually ignored by
+ the `case' insn proper. */
+/* #define CASE_DROPS_THROUGH */
+
+/* Define this to be the smallest number of different values for which it is
+ best to use a jump-table instead of a tree of conditional branches. The
+ default is four for machines with a `casesi' instruction and five otherwise.
+ This is best for most machines. */
+/* #define CASE_VALUES_THRESHOLD */
+
+/* Define this macro if operations between registers with integral mode smaller
+ than a word are always performed on the entire register. Most RISC machines
+ have this property and most CISC machines do not. */
+/* #define WORD_REGISTER_OPERATIONS */
+
+/* Define this macro to be a C expression indicating when insns that read
+ memory in MODE, an integral mode narrower than a word, set the bits outside
+ of MODE to be either the sign-extension or the zero-extension of the data
+ read. Return `SIGN_EXTEND' for values of MODE for which the insn
+ sign-extends, `ZERO_EXTEND' for which it zero-extends, and `NIL' for other
+ modes.
+
+ This macro is not called with MODE non-integral or with a width greater than
+ or equal to `BITS_PER_WORD', so you may return any value in this case. Do
+ not define this macro if it would always return `NIL'. On machines where
+ this macro is defined, you will normally define it as the constant
+ `SIGN_EXTEND' or `ZERO_EXTEND'. */
+/* #define LOAD_EXTEND_OP (MODE) */
+
+/* Define if loading short immediate values into registers sign extends. */
+/* #define SHORT_IMMEDIATES_SIGN_EXTEND */
+
+/* An alias for a tree code that should be used by default for conversion of
+ floating point values to fixed point. Normally, `FIX_ROUND_EXPR' is used. */
+/* #define IMPLICIT_FIX_EXPR */
+
+/* Define this macro if the same instructions that convert a floating point
+ number to a signed fixed point number also convert validly to an unsigned
+ one. */
+/* #define FIXUNS_TRUNC_LIKE_FIX_TRUNC */
+
+/* An alias for a tree code that is the easiest kind of division to compile
+ code for in the general case. It may be `TRUNC_DIV_EXPR', `FLOOR_DIV_EXPR',
+ `CEIL_DIV_EXPR' or `ROUND_DIV_EXPR'. These four division operators differ
+ in how they round the result to an integer. `EASY_DIV_EXPR' is used when it
+ is permissible to use any of those kinds of division and the choice should
+ be made on the basis of efficiency. */
+#define EASY_DIV_EXPR TRUNC_DIV_EXPR
+
+/* The maximum number of bytes that a single instruction can move quickly from
+ memory to memory. */
+#define MOVE_MAX 8
+
+/* The maximum number of bytes that a single instruction can move quickly from
+ memory to memory. If this is undefined, the default is `MOVE_MAX'.
+ Otherwise, it is the constant value that is the largest value that
+ `MOVE_MAX' can have at run-time. */
+/* #define MAX_MOVE_MAX */
+
+/* A C expression that is nonzero if on this machine the number of bits
+ actually used for the count of a shift operation is equal to the number of
+ bits needed to represent the size of the object being shifted. When this
+ macro is non-zero, the compiler will assume that it is safe to omit a
+ sign-extend, zero-extend, and certain bitwise `and' instructions that
+ truncates the count of a shift operation. On machines that have
+ instructions that act on bitfields at variable positions, which may include
+ `bit test' instructions, a nonzero `SHIFT_COUNT_TRUNCATED' also enables
+ deletion of truncations of the values that serve as arguments to bitfield
+ instructions.
+
+ If both types of instructions truncate the count (for shifts) and position
+ (for bitfield operations), or if no variable-position bitfield instructions
+ exist, you should define this macro.
+
+ However, on some machines, such as the 80386 and the 680x0, truncation only
+ applies to shift operations and not the (real or pretended) bitfield
+ operations. Define `SHIFT_COUNT_TRUNCATED' to be zero on such machines.
+ Instead, add patterns to the `md' file that include the implied truncation
+ of the shift instructions.
+
+ You need not define this macro if it would always have the value of zero. */
+/* #define SHIFT_COUNT_TRUNCATED */
+
+/* A C expression which is nonzero if on this machine it is safe to "convert"
+ an integer of INPREC bits to one of OUTPREC bits (where OUTPREC is smaller
+ than INPREC) by merely operating on it as if it had only OUTPREC bits.
+
+ On many machines, this expression can be 1.
+
+ When `TRULY_NOOP_TRUNCATION' returns 1 for a pair of sizes for modes for
+ which `MODES_TIEABLE_P' is 0, suboptimal code can result. If this is the
+ case, making `TRULY_NOOP_TRUNCATION' return 0 in such cases may improve
+ things. */
+#define TRULY_NOOP_TRUNCATION(OUTPREC, INPREC) 1
+
+/* A C expression describing the value returned by a comparison operator with
+ an integral mode and stored by a store-flag instruction (`sCOND') when the
+ condition is true. This description must apply to *all* the `sCOND'
+ patterns and all the comparison operators whose results have a `MODE_INT'
+ mode.
+
+ A value of 1 or -1 means that the instruction implementing the comparison
+ operator returns exactly 1 or -1 when the comparison is true and 0 when the
+ comparison is false. Otherwise, the value indicates which bits of the
+ result are guaranteed to be 1 when the comparison is true. This value is
+ interpreted in the mode of the comparison operation, which is given by the
+ mode of the first operand in the `sCOND' pattern. Either the low bit or the
+ sign bit of `STORE_FLAG_VALUE' be on. Presently, only those bits are used
+ by the compiler.
+
+ If `STORE_FLAG_VALUE' is neither 1 or -1, the compiler will generate code
+ that depends only on the specified bits. It can also replace comparison
+ operators with equivalent operations if they cause the required bits to be
+ set, even if the remaining bits are undefined. For example, on a machine
+ whose comparison operators return an `SImode' value and where
+ `STORE_FLAG_VALUE' is defined as `0x80000000', saying that just the sign bit
+ is relevant, the expression
+
+ (ne:SI (and:SI X (const_int POWER-OF-2)) (const_int 0))
+
+ can be converted to
+
+ (ashift:SI X (const_int N))
+
+ where N is the appropriate shift count to move the bit being tested into the
+ sign bit.
+
+ There is no way to describe a machine that always sets the low-order bit for
+ a true value, but does not guarantee the value of any other bits, but we do
+ not know of any machine that has such an instruction. If you are trying to
+ port GNU CC to such a machine, include an instruction to perform a
+ logical-and of the result with 1 in the pattern for the comparison operators
+ and let us know.
+
+ Often, a machine will have multiple instructions that obtain a value from a
+ comparison (or the condition codes). Here are rules to guide the choice of
+ value for `STORE_FLAG_VALUE', and hence the instructions to be used:
+
+ * Use the shortest sequence that yields a valid definition for
+ `STORE_FLAG_VALUE'. It is more efficient for the compiler to
+ "normalize" the value (convert it to, e.g., 1 or 0) than for
+ the comparison operators to do so because there may be
+ opportunities to combine the normalization with other
+ operations.
+
+ * For equal-length sequences, use a value of 1 or -1, with -1
+ being slightly preferred on machines with expensive jumps and
+ 1 preferred on other machines.
+
+ * As a second choice, choose a value of `0x80000001' if
+ instructions exist that set both the sign and low-order bits
+ but do not define the others.
+
+ * Otherwise, use a value of `0x80000000'.
+
+ Many machines can produce both the value chosen for `STORE_FLAG_VALUE' and
+ its negation in the same number of instructions. On those machines, you
+ should also define a pattern for those cases, e.g., one matching
+
+ (set A (neg:M (ne:M B C)))
+
+ Some machines can also perform `and' or `plus' operations on condition code
+ values with less instructions than the corresponding `sCOND' insn followed
+ by `and' or `plus'. On those machines, define the appropriate patterns.
+ Use the names `incscc' and `decscc', respectively, for the the patterns
+ which perform `plus' or `minus' operations on condition code values. See
+ `rs6000.md' for some examples. The GNU Superoptizer can be used to find
+ such instruction sequences on other machines.
+
+ You need not define `STORE_FLAG_VALUE' if the machine has no store-flag
+ instructions. */
+/* #define STORE_FLAG_VALUE */
+
+/* A C expression that gives a non-zero floating point value that is returned
+ when comparison operators with floating-point results are true. Define this
+ macro on machine that have comparison operations that return floating-point
+ values. If there are no such operations, do not define this macro. */
+/* #define FLOAT_STORE_FLAG_VALUE */
+
+/* An alias for the machine mode for pointers. On most machines, define this
+ to be the integer mode corresponding to the width of a hardware pointer;
+ `SImode' on 32-bit machine or `DImode' on 64-bit machines. On some machines
+ you must define this to be one of the partial integer modes, such as
+ `PSImode'.
+
+ The width of `Pmode' must be at least as large as the value of
+ `POINTER_SIZE'. If it is not equal, you must define the macro
+ `POINTERS_EXTEND_UNSIGNED' to specify how pointers are extended to `Pmode'. */
+#define Pmode SImode
+
+/* An alias for the machine mode used for memory references to functions being
+ called, in `call' RTL expressions. On most machines this should be
+ `QImode'. */
+#define FUNCTION_MODE QImode
+
+/* A C expression for the maximum number of instructions above which the
+ function DECL should not be inlined. DECL is a `FUNCTION_DECL' node.
+
+ The default definition of this macro is 64 plus 8 times the number of
+ arguments that the function accepts. Some people think a larger threshold
+ should be used on RISC machines. */
+/* #define INTEGRATE_THRESHOLD(DECL) */
+
+/* Define this if the preprocessor should ignore `#sccs' directives and print
+ no error message.
+
+ Defined in svr4.h. */
+/* #define SCCS_DIRECTIVE */
+
+/* Define this macro if the system header files support C++ as well as C. This
+ macro inhibits the usual method of using system header files in C++, which
+ is to pretend that the file's contents are enclosed in `extern "C" {...}'. */
+/* #define NO_IMPLICIT_EXTERN_C */
+
+/* Define this macro if you want to implement any pragmas. If defined, it
+ should be a C expression to be executed when #pragma is seen. The
+ argument GETC is a function which will return the next character in the
+ input stream, or EOF if no characters are left. The argument UNGETC is
+ a function which will push a character back into the input stream. The
+ argument NAME is the word following #pragma in the input stream. The input
+ stream pointer will be pointing just beyond the end of this word. The
+ expression should return true if it handled the pragma, false otherwise.
+ The input stream should be left undistrubed if false is returned, otherwise
+ it should be pointing at the next character after the end of the pragma.
+ Any characters left between the end of the pragma and the end of the line will
+ be ignored.
+
+ It is generally a bad idea to implement new uses of `#pragma'. The only
+ reason to define this macro is for compatibility with other compilers that
+ do support `#pragma' for the sake of any user programs which already use it. */
+/* #define HANDLE_PRAGMA(GETC, UNGETC, NAME) handle_pragma (GETC, UNGETC, NAME) */
+
+/* Define this macro to handle System V style pragmas: #pragma pack and
+ #pragma weak. Note, #pragma weak will only be supported if SUPPORT_WEAK is
+ defined.
+
+ Defined in svr4.h. */
+#define HANDLE_SYSV_PRAGMA
+
+/* Define this macro to control use of the character `$' in identifier names.
+ The value should be 0, 1, or 2. 0 means `$' is not allowed by default; 1
+ means it is allowed by default if `-traditional' is used; 2 means it is
+ allowed by default provided `-ansi' is not used. 1 is the default; there is
+ no need to define this macro in that case. */
+/* #define DOLLARS_IN_IDENTIFIERS */
+
+/* Define this macro if the assembler does not accept the character `$' in
+ label names. By default constructors and destructors in G++ have `$' in the
+ identifiers. If this macro is defined, `.' is used instead.
+
+ Defined in svr4.h. */
+/* #define NO_DOLLAR_IN_LABEL */
+
+/* Define this macro if the assembler does not accept the character `.' in
+ label names. By default constructors and destructors in G++ have names that
+ use `.'. If this macro is defined, these names are rewritten to avoid `.'. */
+/* #define NO_DOT_IN_LABEL */
+
+/* Define this macro if the target system expects every program's `main'
+ function to return a standard "success" value by default (if no other value
+ is explicitly returned).
+
+ The definition should be a C statement (sans semicolon) to generate the
+ appropriate rtl instructions. It is used only when compiling the end of
+ `main'. */
+/* #define DEFAULT_MAIN_RETURN */
+
+/* Define this if the target system supports the function `atexit' from the
+ ANSI C standard. If this is not defined, and `INIT_SECTION_ASM_OP' is not
+ defined, a default `exit' function will be provided to support C++.
+
+ Defined by svr4.h */
+/* #define HAVE_ATEXIT */
+
+/* Define this if your `exit' function needs to do something besides calling an
+ external function `_cleanup' before terminating with `_exit'. The
+ `EXIT_BODY' macro is only needed if netiher `HAVE_ATEXIT' nor
+ `INIT_SECTION_ASM_OP' are defined. */
+/* #define EXIT_BODY */
+
+/* Define this macro as a C expression that is nonzero if it is safe for the
+ delay slot scheduler to place instructions in the delay slot of INSN, even
+ if they appear to use a resource set or clobbered in INSN. INSN is always a
+ `jump_insn' or an `insn'; GNU CC knows that every `call_insn' has this
+ behavior. On machines where some `insn' or `jump_insn' is really a function
+ call and hence has this behavior, you should define this macro.
+
+ You need not define this macro if it would always return zero. */
+/* #define INSN_SETS_ARE_DELAYED(INSN) */
+
+/* Define this macro as a C expression that is nonzero if it is safe for the
+ delay slot scheduler to place instructions in the delay slot of INSN, even
+ if they appear to set or clobber a resource referenced in INSN. INSN is
+ always a `jump_insn' or an `insn'. On machines where some `insn' or
+ `jump_insn' is really a function call and its operands are registers whose
+ use is actually in the subroutine it calls, you should define this macro.
+ Doing so allows the delay slot scheduler to move instructions which copy
+ arguments into the argument registers into the delay slot of INSN.
+
+ You need not define this macro if it would always return zero. */
+/* #define INSN_REFERENCES_ARE_DELAYED(INSN) */
+
+/* #define MACHINE_DEPENDENT_REORG(INSN) fr30_reorg (INSN) */
+
+/* Define this macro if in some cases global symbols from one translation unit
+ may not be bound to undefined symbols in another translation unit without
+ user intervention. For instance, under Microsoft Windows symbols must be
+ explicitly imported from shared libraries (DLLs). */
+/* #define MULTIPLE_SYMBOL_SPACES */
+
+/* A C expression for the maximum number of instructions to execute via
+ conditional execution instructions instead of a branch. A value of
+ BRANCH_COST+1 is the default if the machine does not use
+ cc0, and 1 if it does use cc0. */
+/* #define MAX_CONDITIONAL_EXECUTE */
+
+/* Indicate how many instructions can be issued at the same time. */
+/* #define ISSUE_RATE */
+
+/* If cross-compiling, don't require stdio.h etc to build libgcc.a. */
+#if defined CROSS_COMPILE && ! defined inhibit_libc
+#define inhibit_libc
+#endif
+
+/*}}}*/ \f
+/*{{{ Exported variables */
+
+/* Define the information needed to generate branch and scc insns. This is
+ stored from the compare operation. Note that we can't use "rtx" here
+ since it hasn't been defined! */
+
+extern struct rtx_def * fr30_compare_op0;
+extern struct rtx_def * fr30_compare_op1;
+
+/*}}}*/ \f
+/*{{{ PERDICATE_CODES */
+
+#define PREDICATE_CODES \
+ { "stack_add_operand", { CONST_INT }}, \
+ { "high_register_operand", { REG }}, \
+ { "low_register_operand", { REG }}, \
+ { "call_operand", { REG, MEM }}, \
+ { "fp_displacement_operand", { CONST_INT }}, \
+ { "sp_displacement_operand", { CONST_INT }}, \
+ { "add_immediate_operand", { REG, CONST_INT }},
+
+/*}}}*/ \f
+/*{{{ Functions defined in fr30.c */
+
+extern void fr30_expand_prologue PROTO ((void));
+extern void fr30_expand_epilogue PROTO ((void));
+extern unsigned int fr30_compute_frame_size PROTO ((int, int));
+extern int fr30_check_multiple_regs PROTO ((Rtx *, int, int));
+extern Rtx fr30_va_arg PROTO ((Tree, Tree));
+#ifndef NO_MD_PROTOTYPES
+extern int stack_add_operand PROTO ((Rtx, Mmode));
+extern int add_immediate_operand PROTO ((Rtx, Mmode));
+extern int high_register_operand PROTO ((Rtx, Mmode));
+extern int low_register_operand PROTO ((Rtx, Mmode));
+extern int call_operand PROTO ((Rtx, Mmode));
+#endif
+
+/*}}}*/ \f
+
+/* Local Variables: */
+/* folded-file: t */
+/* End: */
projects / platform / upstream / linaro-gcc.git / commitdiff