e6bf48d110
As of revea222be0d, 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 sinceea222be0dbut 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.
39 lines
1.2 KiB
LLVM
39 lines
1.2 KiB
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc < %s -mtriple=i386-unknown-linux-gnu | FileCheck %s
|
|
|
|
define i32 @a() nounwind {
|
|
; CHECK-LABEL: a:
|
|
; CHECK: # %bb.0: # %entry
|
|
; CHECK-NEXT: pushl %esi
|
|
; CHECK-NEXT: subl $8, %esp
|
|
; CHECK-NEXT: leal {{[0-9]+}}(%esp), %esi
|
|
; CHECK-NEXT: movl %esi, %eax
|
|
; CHECK-NEXT: subl $a, %eax
|
|
; CHECK-NEXT: calll d@PLT
|
|
; CHECK-NEXT: cmpl $a, %esi
|
|
; CHECK-NEXT: jbe .LBB0_2
|
|
; CHECK-NEXT: .p2align 4
|
|
; CHECK-NEXT: .LBB0_1: # %for.cond
|
|
; CHECK-NEXT: # =>This Inner Loop Header: Depth=1
|
|
; CHECK-NEXT: jmp .LBB0_1
|
|
; CHECK-NEXT: .LBB0_2: # %for.end.split
|
|
; CHECK-NEXT: addl $8, %esp
|
|
; CHECK-NEXT: popl %esi
|
|
; CHECK-NEXT: retl
|
|
entry:
|
|
%b = alloca i32, align 4
|
|
%0 = ptrtoint ptr %b to i32
|
|
%sub = sub nsw i32 %0, ptrtoint (ptr @a to i32)
|
|
%call = call i32 @d(i32 inreg %sub)
|
|
%cmp = icmp ugt ptr %b, @a
|
|
br i1 %cmp, label %for.cond, label %for.end.split
|
|
|
|
for.cond: ; preds = %entry, %for.cond
|
|
br label %for.cond
|
|
|
|
for.end.split: ; preds = %entry
|
|
ret i32 undef
|
|
}
|
|
|
|
declare i32 @d(...)
|