Skip to content

GitLab

WARNING! Access to this system is limited to authorised users only.
Unauthorised users may be subject to prosecution.
Unauthorised access to this system is a criminal offence under Australian law (Federal Crimes Act 1914 Part VIA)
It is a criminal offence to:
(1) Obtain access to data without authority. -Penalty 2 years imprisonment.
(2) Damage, delete, alter or insert data without authority. -Penalty 10 years imprisonment.
User activity is monitored and recorded. Anyone using this system expressly consents to such monitoring and recording.

Open
Created by Yi Lin@u4776528Owner

Implementing ALLOCA/ALLOCA_HYBRID

Currently the compiler assumes that frame size is constant at compile time.

For x86_64, stack pointer needs to be 16-bytes aligned before a function call. The compiler ensures this by:

  • rbp is always 16-bytes aligned.
  • frame size is a multiple of 16-bytes (align up to 16-bytes if it is not, see frame.rs).
  • if any call argument is passed on stack, if necessary, push a padding value to stack so that rsp is still 16-bytes aligned after pushing call arguments.
  • restoring from an exception will set rsp from rbp and the constant frame size.

We can implement ALLOCA by computing allocating size during compile time, and frame size is still a compile-time constant. However, the implementation of ALLOCA_HYBRID will break this assumption. A straightforward solution is to make the alloca'd size always a multiple of 16-bytes (for alignment requirement), and record a current frame size somewhere (for restoring from exception) - this would keep most of the above unchanged. This issue tracks related discussion.