File: null-ptr-is-valid.ll

package info (click to toggle)
llvm-toolchain-18 1%3A18.1.8-18
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,908,340 kB
  • sloc: cpp: 6,667,937; ansic: 1,440,452; asm: 883,619; python: 230,549; objc: 76,880; f90: 74,238; lisp: 35,989; pascal: 16,571; sh: 10,229; perl: 7,459; ml: 5,047; awk: 3,523; makefile: 2,987; javascript: 2,149; xml: 892; fortran: 649; cs: 573
file content (24 lines) | stat: -rw-r--r-- 765 bytes parent folder | download | duplicates (14) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
; RUN: opt -S -passes=instsimplify < %s | FileCheck %s

target datalayout = "A5"

; A 0 valued byval pointer may be valid
define i1 @byval_may_be_zero(ptr addrspace(5) byval(i32) %ptr) {
; CHECK-LABEL: @byval_may_be_zero(
; CHECK-NEXT:    [[CMP:%.*]] = icmp eq ptr addrspace(5) [[PTR:%.*]], null
; CHECK-NEXT:    ret i1 [[CMP]]
;
  %cmp = icmp eq ptr addrspace(5) %ptr, null
  ret i1 %cmp
}

; FIXME: The interpretation of nonnull assumes a 0 pointer value, so
; this really is an incorrect fold.
define i1 @nonnull_may_be_zero(ptr addrspace(5) nonnull %ptr) {
; CHECK-LABEL: @nonnull_may_be_zero(
; CHECK-NEXT:    ret i1 false
;
  %cmp = icmp eq ptr addrspace(5) %ptr, null
  ret i1 %cmp
}