0609b65aaf
The following commit enabled the analysis of ranges for heap allocations: 22ca38da25e19a7c5fcfeb3f22159aba92ec381e The range turns out to be empty in cases such as the one in test (which is [1,1)), leading to an assertion failure. This patch fixes for the same case. Fixes https://github.com/llvm/llvm-project/issues/63856 Reviewed By: fhahn Differential Revision: https://reviews.llvm.org/D159160
38 lines
1.3 KiB
LLVM
38 lines
1.3 KiB
LLVM
; NOTE: Assertions have been autogenerated by utils/update_analyze_test_checks.py UTC_ARGS: --version 2
|
|
; RUN: opt -passes='print<scalar-evolution>' -disable-output %s 2>&1 | FileCheck %s
|
|
|
|
define ptr @f() {
|
|
; CHECK-LABEL: 'f'
|
|
; CHECK-NEXT: Classifying expressions for: @f
|
|
; CHECK-NEXT: %alloc = tail call dereferenceable(64) ptr @malloc(i64 64)
|
|
; CHECK-NEXT: --> %alloc U: [1,-64) S: full-set
|
|
; CHECK-NEXT: Determining loop execution counts for: @f
|
|
;
|
|
%alloc = tail call dereferenceable(64) ptr @malloc(i64 64)
|
|
ret ptr %alloc
|
|
}
|
|
|
|
define ptr @f2() {
|
|
; CHECK-LABEL: 'f2'
|
|
; CHECK-NEXT: Classifying expressions for: @f2
|
|
; CHECK-NEXT: %alloc = tail call dereferenceable_or_null(64) ptr @malloc(i64 64)
|
|
; CHECK-NEXT: --> %alloc U: [0,-64) S: full-set
|
|
; CHECK-NEXT: Determining loop execution counts for: @f2
|
|
;
|
|
%alloc = tail call dereferenceable_or_null(64) ptr @malloc(i64 64)
|
|
ret ptr %alloc
|
|
}
|
|
|
|
define ptr @undefined_max() {
|
|
; CHECK-LABEL: 'undefined_max'
|
|
; CHECK-NEXT: Classifying expressions for: @undefined_max
|
|
; CHECK-NEXT: %alloc = call nonnull ptr @malloc(i64 -1)
|
|
; CHECK-NEXT: --> %alloc U: full-set S: full-set
|
|
; CHECK-NEXT: Determining loop execution counts for: @undefined_max
|
|
;
|
|
%alloc = call nonnull ptr @malloc(i64 -1)
|
|
ret ptr %alloc
|
|
}
|
|
|
|
declare noalias noundef ptr @malloc(i64 noundef) allockind("alloc,uninitialized") allocsize(0)
|