mono/linux-packaging-mono
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Imported Upstream version 5.18.0.161

Browse Source 
Former-commit-id: 4db48158d3a35497b8f118ab21b5f08ac3d86d98
This commit is contained in:
Xamarin Public Jenkins (auto-signing)
2018-10-19 08:34:24 +00:00
parent 37fbf886a3
commit e19d552987
28702 changed files with 3868076 additions and 803 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
external/llvm/test/MC/X86/AlignedBundling/pad-align-to-bundle-end.s vendored Normal file
View File

@@ -0,0 +1,35 @@
# RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu -mcpu=pentiumpro %s -o - \
# RUN: | llvm-objdump -disassemble -no-show-raw-insn - | FileCheck %s
# RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu -mcpu=pentiumpro -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