llvm-6502/test/CodeGen/XCore/align.ll at fa3d0dc026331bf8b64382874f54ce11cefe51a6 - llvm-6502 - Applefritter: Git

6502/llvm-6502

mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-10-30 16:17:05 +00:00

Files

Richard Osborne 6dc9f732ce [XCore] Prefer to word align functions.

The behaviour of the XCore's instruction buffer means that the performance
of the same code sequence can differ depending on whether it starts at a 4
byte aligned address or not. Since we don't model the instruction buffer
in the backend we have no way of knowing for sure if it is beneficial to
word align a specific function. However, in the absence of precise
modelling, it is better on balance to word align functions because:

* It makes a fetch-nop while executing the prologue slightly less likely.
* If we don't word align functions then a small perturbation in one
  function can have a dramatic knock on effect. If the size of the function
  changes it might change the alignment and therefore the performance of
  all the functions that happen to follow it in the binary. This butterfly
  effect makes it harder to reason about and measure the performance of
  code.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@202163 91177308-0d34-0410-b5e6-96231b3b80d8

2014-02-25 16:37:15 +00:00

16 lines

222 B

LLVM

Raw Blame History

 ; RUN: llc < %s -march=xcore | FileCheck %s
 ; CHECK: .align 4
 ; CHECK-LABEL: f:
 define void @f() nounwind {
 entry:
   ret void
 }
 ; CHECK: .align 2
 ; CHECK-LABEL: g:
 define void @g() nounwind optsize {
 entry:
   ret void
 }