mirror of
https://github.com/RPCS3/llvm.git
synced 2025-05-16 18:35:53 +00:00
90b5ec2f8c
Summary: The value tracking analysis uses function alignment to infer that the least significant bits of function pointers are known to be zero. Unfortunately, this is not correct for ARM targets: the least significant bit of a function pointer stores the ARM/Thumb state information (i.e., the LSB is set for Thumb functions and cleared for ARM functions). The original approach (https://reviews.llvm.org/D44781) introduced a new field for function pointer alignment in the DataLayout structure to address this. But it seems unlikely that optimizations based on function pointer alignment would bring much benefit in practice to justify the additional maintenance burden, so this patch simply assumes that function pointer alignment is always unknown. Reviewers: javed.absar, efriedma Reviewed By: efriedma Subscribers: kristof.beyls, llvm-commits, hfinkel, rogfer01 Differential Revision: https://reviews.llvm.org/D46110 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@331025 91177308-0d34-0410-b5e6-96231b3b80d8
19 lines
470 B
LLVM
19 lines
470 B
LLVM
; RUN: opt -instcombine -S < %s | FileCheck %s
|
|
|
|
target datalayout = "e-p:32:32-n32-S64"
|
|
|
|
; CHECK-LABEL: @foo_ptr
|
|
; CHECK: and
|
|
define i32 @foo_ptr() {
|
|
entry:
|
|
; Even though the address of @foo is aligned, we cannot assume that the
|
|
; pointer has the same alignment. This is not true for e.g. ARM targets
|
|
; which store ARM/Thumb state in the LSB
|
|
ret i32 and (i32 ptrtoint (void ()* @foo to i32), i32 -4)
|
|
}
|
|
|
|
define internal void @foo() align 16 {
|
|
entry:
|
|
ret void
|
|
}
|