llvm-6502/test/MC/X86/AlignedBundling/pad-align-to-bundle-end.s
Petr Hosek 054db7df5b [MC] Write padding into fragments when -mc-relax-all flag is used
Summary:
When instruction bundling is enabled and the -mc-relax-all flag is
set, we can write bundle padding directly into fragments and avoid
creating large number of fragments significantly reducing LLVM MC
memory usage.

Test Plan: Regression test attached

Reviewers: eliben

Subscribers: jfb, mseaborn

Differential Revision: http://reviews.llvm.org/D8072

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@234714 91177308-0d34-0410-b5e6-96231b3b80d8
2015-04-12 23:42:25 +00:00

36 lines
1.1 KiB
ArmAsm

# RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \
# RUN: | llvm-objdump -disassemble -no-show-raw-insn - | FileCheck %s
# RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu -mc-relax-all %s -o - \
# RUN: | llvm-objdump -disassemble -no-show-raw-insn - | FileCheck %s
# Test some variations of padding to the end of a bundle.
.text
foo:
.bundle_align_mode 4
# Each of these callq instructions is 5 bytes long
callq bar
callq bar
.bundle_lock align_to_end
callq bar
.bundle_unlock
# To align this group to a bundle end, we need a 1-byte NOP.
# CHECK: a: nop
# CHECK-NEXT: b: callq
callq bar
callq bar
.bundle_lock align_to_end
callq bar
callq bar
.bundle_unlock
# Here we have to pad until the end of the *next* boundary because
# otherwise the group crosses a boundary.
# CHECK: 1a: nop
# The nop sequence may be implemented as one instruction or many, but if
# it's one instruction, that instruction cannot itself cross the boundary.
# CHECK: 20: nop
# CHECK-NEXT: 26: callq
# CHECK-NEXT: 2b: callq