2019-04-17 12:52:47 +08:00
|
|
|
; RUN: opt -scoped-noalias -basicaa -gvn -S < %s | FileCheck %s
|
|
|
|
|
|
|
|
|
|
define i32 @test1(i32* %p, i32* %q) {
|
|
|
|
|
; CHECK-LABEL: @test1(i32* %p, i32* %q)
|
|
|
|
|
; CHECK: load i32, i32* %p
|
|
|
|
|
; CHECK-NOT: noalias
|
|
|
|
|
; CHECK: %c = add i32 %a, %a
|
|
|
|
|
%a = load i32, i32* %p, !noalias !0
|
|
|
|
|
%b = load i32, i32* %p
|
|
|
|
|
%c = add i32 %a, %b
|
|
|
|
|
ret i32 %c
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
define i32 @test2(i32* %p, i32* %q) {
|
|
|
|
|
; CHECK-LABEL: @test2(i32* %p, i32* %q)
|
Infer alignment of unmarked loads in IR/bitcode parsing.
For IR generated by a compiler, this is really simple: you just take the
datalayout from the beginning of the file, and apply it to all the IR
later in the file. For optimization testcases that don't care about the
datalayout, this is also really simple: we just use the default
datalayout.
The complexity here comes from the fact that some LLVM tools allow
overriding the datalayout: some tools have an explicit flag for this,
some tools will infer a datalayout based on the code generation target.
Supporting this properly required plumbing through a bunch of new
machinery: we want to allow overriding the datalayout after the
datalayout is parsed from the file, but before we use any information
from it. Therefore, IR/bitcode parsing now has a callback to allow tools
to compute the datalayout at the appropriate time.
Not sure if I covered all the LLVM tools that want to use the callback.
(clang? lli? Misc IR manipulation tools like llvm-link?). But this is at
least enough for all the LLVM regression tests, and IR without a
datalayout is not something frontends should generate.
This change had some sort of weird effects for certain CodeGen
regression tests: if the datalayout is overridden with a datalayout with
a different program or stack address space, we now parse IR based on the
overridden datalayout, instead of the one written in the file (or the
default one, if none is specified). This broke a few AVR tests, and one
AMDGPU test.
Outside the CodeGen tests I mentioned, the test changes are all just
fixing CHECK lines and moving around datalayout lines in weird places.
Differential Revision: https://reviews.llvm.org/D78403
2020-05-15 03:59:45 +08:00
|
|
|
; CHECK: load i32, i32* %p, align 4, !alias.scope !0
|
2019-04-17 12:52:47 +08:00
|
|
|
; CHECK: %c = add i32 %a, %a
|
|
|
|
|
%a = load i32, i32* %p, !alias.scope !0
|
|
|
|
|
%b = load i32, i32* %p, !alias.scope !0
|
|
|
|
|
%c = add i32 %a, %b
|
|
|
|
|
ret i32 %c
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
; FIXME: In this case we can do better than intersecting the scopes, and can
|
|
|
|
|
; concatenate them instead. Both loads are in the same basic block, the first
|
|
|
|
|
; makes the second safe to speculatively execute, and there are no calls that may
|
|
|
|
|
; throw in between.
|
|
|
|
|
define i32 @test3(i32* %p, i32* %q) {
|
|
|
|
|
; CHECK-LABEL: @test3(i32* %p, i32* %q)
|
Infer alignment of unmarked loads in IR/bitcode parsing.
For IR generated by a compiler, this is really simple: you just take the
datalayout from the beginning of the file, and apply it to all the IR
later in the file. For optimization testcases that don't care about the
datalayout, this is also really simple: we just use the default
datalayout.
The complexity here comes from the fact that some LLVM tools allow
overriding the datalayout: some tools have an explicit flag for this,
some tools will infer a datalayout based on the code generation target.
Supporting this properly required plumbing through a bunch of new
machinery: we want to allow overriding the datalayout after the
datalayout is parsed from the file, but before we use any information
from it. Therefore, IR/bitcode parsing now has a callback to allow tools
to compute the datalayout at the appropriate time.
Not sure if I covered all the LLVM tools that want to use the callback.
(clang? lli? Misc IR manipulation tools like llvm-link?). But this is at
least enough for all the LLVM regression tests, and IR without a
datalayout is not something frontends should generate.
This change had some sort of weird effects for certain CodeGen
regression tests: if the datalayout is overridden with a datalayout with
a different program or stack address space, we now parse IR based on the
overridden datalayout, instead of the one written in the file (or the
default one, if none is specified). This broke a few AVR tests, and one
AMDGPU test.
Outside the CodeGen tests I mentioned, the test changes are all just
fixing CHECK lines and moving around datalayout lines in weird places.
Differential Revision: https://reviews.llvm.org/D78403
2020-05-15 03:59:45 +08:00
|
|
|
; CHECK: load i32, i32* %p, align 4, !alias.scope !1
|
2019-04-17 12:52:47 +08:00
|
|
|
; CHECK: %c = add i32 %a, %a
|
|
|
|
|
%a = load i32, i32* %p, !alias.scope !1
|
|
|
|
|
%b = load i32, i32* %p, !alias.scope !2
|
|
|
|
|
%c = add i32 %a, %b
|
|
|
|
|
ret i32 %c
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
declare i32 @foo(i32*) readonly
|
|
|
|
|
|
|
|
|
|
!0 = !{!0}
|
|
|
|
|
!1 = !{!1}
|
|
|
|
|
!2 = !{!0, !1}
|
|
|
|
|
|