e6bf48d110
As of rev ea222be0d, LLVMs assembler will actually try to honour the "fill value" part of p2align directives. X86 printed these as 0x90, which isn't actually what it wanted: we want multi-byte nops for .text padding. Compiling via a textual assembly file produces single-byte nop padding since ea222be0d but the built-in assembler will produce multi-byte nops. This divergent behaviour is undesirable. To fix: don't set the byte padding field for x86, which allows the assembler to pick multi-byte nops. Test that we get the same multi-byte padding when compiled via textual assembly or directly to object file. Added same-align-bytes-with-llasm-llobj.ll to that effect, updated numerous other tests to not contain check-lines for the explicit padding.
16 lines
466 B
C
16 lines
466 B
C
// REQUIRES: x86-registered-target
|
|
/// Check asm because we use llvm::TargetOptions.
|
|
|
|
// RUN: %clang_cc1 -triple=x86_64 -S %s -falign-loops=8 -O -o - | FileCheck %s --check-prefixes=CHECK,CHECK_8
|
|
// RUN: %clang_cc1 -triple=x86_64 -S %s -falign-loops=32 -O -o - | FileCheck %s --check-prefixes=CHECK,CHECK_32
|
|
|
|
// CHECK-LABEL: foo:
|
|
// CHECK_8: .p2align 3
|
|
// CHECK_32: .p2align 5
|
|
|
|
void bar(void);
|
|
void foo(void) {
|
|
for (int i = 0; i < 64; ++i)
|
|
bar();
|
|
}
|