/*--------------------------------------------------------------------------- Main data structures ---------------------------------------------------------------------------*/ /* A tree node can represent a data type, a variable, an expression or a statement. Each node has a TREE_CODE which says what kind of thing it represents. Some common codes are: INTEGER_TYPE -- represents a type of integers. ARRAY_TYPE -- represents a type of pointer. VAR_DECL -- represents a declared variable. INTEGER_CST -- represents a constant integer value. PLUS_EXPR -- represents a sum (an expression).
As for the contents of a tree node: there are some fields that all nodes share. Each TREE_CODE has various special-purpose fields as well. The fields of a node are never accessed directly, always through accessor macros. */
/* Every kind of tree node starts with this structure, so all nodes have these fields.
See the accessor macros, defined below, for documentation of the fields, and the table below which connects the fields and the accessor macros. */
struct GTY(()) tree_base { ENUM_BITFIELD(tree_code) code : 16;
unsigned side_effects_flag : 1; unsigned constant_flag : 1; unsigned addressable_flag : 1; unsigned volatile_flag : 1; unsigned readonly_flag : 1; unsigned asm_written_flag: 1; unsigned nowarning_flag : 1; unsigned visited : 1;
unsigned used_flag : 1; unsigned nothrow_flag : 1; unsigned static_flag : 1; unsigned public_flag : 1; unsigned private_flag : 1; unsigned protected_flag : 1; unsigned deprecated_flag : 1; unsigned default_def_flag : 1;
union { /* The bits in the following structure should only be used with accessor macros that constrain inputs with tree checking. */ struct { unsigned lang_flag_0 : 1; unsigned lang_flag_1 : 1; unsigned lang_flag_2 : 1; unsigned lang_flag_3 : 1; unsigned lang_flag_4 : 1; unsigned lang_flag_5 : 1; unsigned lang_flag_6 : 1; unsigned saturating_flag : 1;
unsigned unsigned_flag : 1; unsigned packed_flag : 1; unsigned user_align : 1; unsigned nameless_flag : 1; unsigned atomic_flag : 1; unsigned spare0 : 3;
unsigned spare1 : 8;
/* This field is only used with TREE_TYPE nodes; the only reason it is present in tree_base instead of tree_type is to save space. The size of the field must be large enough to hold addr_space_t values. */ unsigned address_space : 8; } bits;
/* The following fields are present in tree_base to save space. The nodes using them do not require any of the flags above and so can make better use of the 4-byte sized word. */
/* The number of HOST_WIDE_INTs in an INTEGER_CST. */ struct { /* The number of HOST_WIDE_INTs if the INTEGER_CST is accessed in its native precision. */ unsigned char unextended;
/* The number of HOST_WIDE_INTs if the INTEGER_CST is extended to wider precisions based on its TYPE_SIGN. */ unsigned char extended;
/* The number of HOST_WIDE_INTs if the INTEGER_CST is accessed in offset_int precision, with smaller integers being extended according to their TYPE_SIGN. This is equal to one of the two fields above but is cached for speed. */ unsigned char offset; } int_length;
/* VEC length. This field is only used with TREE_VEC. */ int length;
/* SSA version number. This field is only used with SSA_NAME. */ unsigned int version;
/* Internal function code. */ enum internal_fn ifn;
/* The following two fields are used for MEM_REF and TARGET_MEM_REF expression trees and specify known data non-dependences. For two memory references in a function they are known to not alias if dependence_info.clique are equal and dependence_info.base are distinct. */ struct { unsigned short clique; unsigned short base; } dependence_info; } GTY((skip(""))) u; };
GCC主要数据结构之tree_base
最新推荐文章于 2024-06-09 15:18:03 发布