File: allocsize-32.ll

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (29 lines) | stat: -rw-r--r-- 932 bytes parent folder | download | duplicates (17) 
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 -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 i8* @my_malloc(i8*, i64) allocsize(1)

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

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

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

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

declare i32 @llvm.objectsize.i32.p0i8(i8*, i1)