Next: , Up: GIMPLE   [Contents][Index]


12.1 Tuple representation

GIMPLE instructions are tuples of variable size divided in two groups: a header describing the instruction and its locations, and a variable length body with all the operands. Tuples are organized into a hierarchy with 3 main classes of tuples.

12.1.1 gimple (gsbase)

This is the root of the hierarchy, it holds basic information needed by most GIMPLE statements. There are some fields that may not be relevant to every GIMPLE statement, but those were moved into the base structure to take advantage of holes left by other fields (thus making the structure more compact). The structure takes 4 words (32 bytes) on 64 bit hosts:

FieldSize (bits)
code8
subcode16
no_warning1
visited1
nontemporal_move1
plf2
modified1
has_volatile_ops1
references_memory_p1
uid32
location32
num_ops32
bb64
block63
Total size32 bytes

12.1.2 gimple_statement_with_ops

This tuple is actually split in two: gimple_statement_with_ops_base and gimple_statement_with_ops. This is needed to accommodate the way the operand vector is allocated. The operand vector is defined to be an array of 1 element. So, to allocate a dynamic number of operands, the memory allocator (gimple_alloc) simply allocates enough memory to hold the structure itself plus N - 1 operands which run “off the end” of the structure. For example, to allocate space for a tuple with 3 operands, gimple_alloc reserves sizeof (struct gimple_statement_with_ops) + 2 * sizeof (tree) bytes.

On the other hand, several fields in this tuple need to be shared with the gimple_statement_with_memory_ops tuple. So, these common fields are placed in gimple_statement_with_ops_base which is then inherited from the other two tuples.

gsbase256
def_ops64
use_ops64
opnum_ops * 64
Total size48 + 8 * num_ops bytes

12.1.3 gimple_statement_with_memory_ops

This tuple is essentially identical to gimple_statement_with_ops, except that it contains 4 additional fields to hold vectors related memory stores and loads. Similar to the previous case, the structure is split in two to accommodate for the operand vector (gimple_statement_with_memory_ops_base and gimple_statement_with_memory_ops).

FieldSize (bits)
gsbase256
def_ops64
use_ops64
vdef_ops64
vuse_ops64
stores64
loads64
opnum_ops * 64
Total size80 + 8 * num_ops bytes

All the other tuples are defined in terms of these three basic ones. Each tuple will add some fields.


Next: , Up: GIMPLE   [Contents][Index]