GitLab

Taking explicit size+po2align makes things easier compared to the
previously used ir_type: ir_type* is a middleend concept not everything
in the backend is represented as a type/mode anymore (x86_insn_size_t).
Furthermore we only respected size+alignment of that type anyway,
additional semantics would be unexpectedly ignored. It also simplifies
the code in some places.

This should also naturally fix a problem in 188.amp where we wrongly
passed the type for mode_Ls instead of the type for mode_D before.

Nearly all structs derived from amd64_attr_t has a size member anyway.
Simplify the code and move it to the base amd64_attr_t.

We only use the immediate and scale yet on ia32.

This is a bigger rewrite of stack frame handling in the backend:

- Do the stack frame type layout late, after all the spill slots have
  been created. This way we can avoid (and remove) the brittle
  frame_alloc_area().
- Standardize the meaning of stack entity offsets. After stack frame type
  layout they are relative to the stack pointer position at the beginning
  of the function.  It is all in one type now, no splitting into "arg",
  "between" and "stack_frame" type anymore.
- Generalize the stack pointer simulation code to work with a single
  callback. Represent stack state as current offset and align_padding
  number. Now that callbacks can access and modify them both we do not
  need custom code in the sparc backend anymore.
- Remove alignment specification on IncSP, only keep a ignore_align flag
  used for the last IncSP that has to remove all existing sp adjustments
  and may end up on a misaligned SP on ia32/amd64.
- Align stack by default on ia32+amd64 backends.

They previously used be_stack_layout but that structure will be remove
soon.

This allows us to properly implement the OS X calling conventions.

This fixes backend/long_double_arith.c.

This plugs a memory leak.

Commit d33e0668 accidentally disabled
varargs support unless long double support is enabled.

Also disable it by default for now until x87 support is more mature.

We can see that we need a frame entity if the the immediate has a
X86_IMM_FRAMEOFFSET relocation but no entity assigned yet.

be: Pass the input requirements directly to the constructors of nodes, which have a variable number of arguments.