llvm-6502/test/MC/ARM/AlignedBundling/group-bundle-arm.s
Derek Schuff 67144e37ba If bundle alignment is enabled, do not add data to a fragment with instructions
With bundle alignment, instructions all get their own MCFragments
(unless they are in a bundle-locked group). For instructions with
fixups, this is an MCDataFragment. Emitting actual data (e.g. for
.long) attempts to re-use MCDataFragments, which we don't want int
this case since it leads to fragments which exceed the bundle size.
So, don't reuse them in this case.
Also adds a test and fixes some formatting.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@175316 91177308-0d34-0410-b5e6-96231b3b80d8
2013-02-15 22:50:52 +00:00

49 lines
876 B
ArmAsm

# RUN: llvm-mc -filetype=obj -triple armv7-linux-gnueabi %s -o - \
# RUN: | llvm-objdump -no-show-raw-insn -triple armv7 -disassemble - | FileCheck %s
# On ARM each instruction is 4 bytes long so padding for individual
# instructions should not be inserted. However, for bundle-locked groups
# it can be.
.syntax unified
.text
.bundle_align_mode 4
bx lr
and r1, r1, r2
and r1, r1, r2
.bundle_lock
bx r9
bx r8
.bundle_unlock
# CHECK: c: nop
# CHECK-NEXT: 10: bx
# CHECK-NEXT: 14: bx
# pow2 here
.align 4
bx lr
.bundle_lock
bx r9
bx r9
bx r9
bx r8
.bundle_unlock
# CHECK: 20: bx
# CHECK-NEXT: 24: nop
# CHECK-NEXT: 28: nop
# CHECK-NEXT: 2c: nop
# CHECK-NEXT: 30: bx
.align 4
foo:
b foo
.long 3892240112
.long 3892240112
.long 3892240112
.long 3892240112
.long 3892240112
.long 3892240112
# CHECK: 40: b