1; RUN: opt < %s -passes=instcombine -S | FileCheck %s 2; 3; The idea is that we want to have sane semantics (e.g. not assertion failures) 4; when given an allocsize function that takes a 64-bit argument in the face of 5; 32-bit pointers. 6 7target datalayout="e-p:32:32:32" 8 9declare ptr @my_malloc(ptr, i64) allocsize(1) 10 11define void @test_malloc(ptr %p, ptr %r) { 12 %1 = call ptr @my_malloc(ptr null, i64 100) 13 store ptr %1, ptr %p, align 8 ; To ensure objectsize isn't killed 14 15 %2 = call i32 @llvm.objectsize.i32.p0(ptr %1, i1 false) 16 ; CHECK: store i32 100 17 store i32 %2, ptr %r, align 8 18 19 ; Big number is 5 billion. 20 %3 = call ptr @my_malloc(ptr null, i64 5000000000) 21 store ptr %3, ptr %p, align 8 ; To ensure objectsize isn't killed 22 23 ; CHECK: call i32 @llvm.objectsize 24 %4 = call i32 @llvm.objectsize.i32.p0(ptr %3, i1 false) 25 store i32 %4, ptr %r, align 8 26 ret void 27} 28 29declare i32 @llvm.objectsize.i32.p0(ptr, i1) 30