2caaec65c0
Due to an improvement to name preservation, a lot of InstCombine tests now show spurious diffs when regenerated. Rather than regenerating individual files when they get touched, mass-regenerate all UTC-based InstCombine tests. I have then reset a number of files showing suspicious diffs where the UTC output has clearly been manually adjusted. I apologize if I missed anything in the mass of changes.
27 lines
1002 B
LLVM
27 lines
1002 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --version 2
|
|
; Regression test for PR51200.
|
|
;
|
|
; RUN: opt < %s -passes=instcombine -S | FileCheck %s
|
|
;
|
|
; This transformation requires the pointer size, as it assumes that size_t is
|
|
; the size of a pointer.
|
|
|
|
@percent_s = constant [3 x i8] c"%s\00"
|
|
|
|
declare i32 @sprintf(ptr, ptr, ...)
|
|
|
|
define i32 @PR51200(ptr %p, ptr %p2) {
|
|
; CHECK-LABEL: define i32 @PR51200
|
|
; CHECK-SAME: (ptr [[P:%.*]], ptr [[P2:%.*]]) {
|
|
; CHECK-NEXT: [[STPCPY:%.*]] = call ptr @stpcpy(ptr [[P]], ptr [[P2]])
|
|
; CHECK-NEXT: [[TMP1:%.*]] = ptrtoint ptr [[STPCPY]] to i64
|
|
; CHECK-NEXT: [[TMP2:%.*]] = ptrtoint ptr [[P]] to i64
|
|
; CHECK-NEXT: [[TMP3:%.*]] = sub i64 [[TMP1]], [[TMP2]]
|
|
; CHECK-NEXT: [[CALL:%.*]] = trunc i64 [[TMP3]] to i32
|
|
; CHECK-NEXT: ret i32 [[CALL]]
|
|
;
|
|
; Don't check anything, just expect the test to compile successfully.
|
|
%call = call i32 (ptr, ptr, ...) @sprintf(ptr %p, ptr @percent_s, ptr %p2)
|
|
ret i32 %call
|
|
}
|