File: allocsize-32.ll

package info (click to toggle)
llvm-toolchain-17 1%3A17.0.6-22
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,799,624 kB
  • sloc: cpp: 6,428,607; ansic: 1,383,196; asm: 793,408; python: 223,504; objc: 75,364; f90: 60,502; lisp: 33,869; pascal: 15,282; sh: 9,684; perl: 7,453; ml: 4,937; awk: 3,523; makefile: 2,889; javascript: 2,149; xml: 888; fortran: 619; cs: 573
file content (29 lines) | stat: -rw-r--r-- 927 bytes parent folder | download | duplicates (12) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
 
; RUN: opt < %s -passes=instcombine -S | FileCheck %s
;
; The idea is that we want to have sane semantics (e.g. not assertion failures)
; when given an allocsize function that takes a 64-bit argument in the face of
; 32-bit pointers.

target datalayout="e-p:32:32:32"

declare ptr @my_malloc(ptr, i64) allocsize(1)

define void @test_malloc(ptr %p, ptr %r) {
  %1 = call ptr @my_malloc(ptr null, i64 100)
  store ptr %1, ptr %p, align 8 ; To ensure objectsize isn't killed

  %2 = call i32 @llvm.objectsize.i32.p0(ptr %1, i1 false)
  ; CHECK: store i32 100
  store i32 %2, ptr %r, align 8

  ; Big number is 5 billion.
  %3 = call ptr @my_malloc(ptr null, i64 5000000000)
  store ptr %3, ptr %p, align 8 ; To ensure objectsize isn't killed

  ; CHECK: call i32 @llvm.objectsize
  %4 = call i32 @llvm.objectsize.i32.p0(ptr %3, i1 false)
  store i32 %4, ptr %r, align 8
  ret void
}

declare i32 @llvm.objectsize.i32.p0(ptr, i1)