diff options
| author | David Majnemer <david.majnemer@gmail.com> | 2013-09-26 09:18:48 +0000 |
|---|---|---|
| committer | David Majnemer <david.majnemer@gmail.com> | 2013-09-26 09:18:48 +0000 |
| commit | 9637da60835a60f8ccd8289d04c60b2dcd4b9b5a (patch) | |
| tree | 318798785545cf2297ca76cea962e40844aad6fc /test/MC/PowerPC | |
| parent | 6b4e9ba21855b1f69c33bdaf416fdb88064aa9fe (diff) | |
| download | external_llvm-9637da60835a60f8ccd8289d04c60b2dcd4b9b5a.zip external_llvm-9637da60835a60f8ccd8289d04c60b2dcd4b9b5a.tar.gz external_llvm-9637da60835a60f8ccd8289d04c60b2dcd4b9b5a.tar.bz2 | |
PPC: Allow partial fills in writeNopData()
When asked to pad an irregular number of bytes, we should fill with
zeros. This is consistent with the behavior specified in the AIX
Assembler Language Reference as well as other LLVM and binutils
assemblers.
N.B. There is a small deviation from binutils' PPC assembler:
when handling pads which are greater than 4 bytes but not mod 4,
binutils will not emit any NOP sequences at all and only use zeros.
This may or may not be a bug but there is no excellent rationale as to
why that behavior is important to emulate. If that behavior is needed,
we can change writeNopData() to behave in the same way.
This fixes PR17352.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191426 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/MC/PowerPC')
| -rw-r--r-- | test/MC/PowerPC/ppc-nop.s | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/test/MC/PowerPC/ppc-nop.s b/test/MC/PowerPC/ppc-nop.s index 567943c..50afae2 100644 --- a/test/MC/PowerPC/ppc-nop.s +++ b/test/MC/PowerPC/ppc-nop.s @@ -5,5 +5,8 @@ blr .p2align 3 blr -# CHECK: 0000: 4E800020 60000000 4E800020 +.byte 0x42 +.p2align 2 + +# CHECK: 0000: 4E800020 60000000 4E800020 42000000 |