This adds -no-opaque-pointers to clang tests whose output will change when opaque pointers are enabled by default. This is intended to be part of the migration approach described in https://discourse.llvm.org/t/enabling-opaque-pointers-by-default/61322/9. The patch has been produced by replacing %clang_cc1 with %clang_cc1 -no-opaque-pointers for tests that fail with opaque pointers enabled. Worth noting that this doesn't cover all tests, there's a remaining ~40 tests not using %clang_cc1 that will need a followup change. Differential Revision: https://reviews.llvm.org/D123115
20 lines
828 B
C
20 lines
828 B
C
// NOTE: Assertions have been autogenerated by utils/update_cc_test_checks.py
|
|
// RUN: %clang_cc1 -no-opaque-pointers -triple x86_64-linux-gnu -emit-llvm %s -o - | FileCheck %s
|
|
|
|
char buffer[32] = "This is a largely unused buffer";
|
|
|
|
// __builtin___clear_cache always maps to @llvm.clear_cache, but what
|
|
// each back-end produces is different, and this is tested in LLVM
|
|
|
|
// CHECK-LABEL: @main(
|
|
// CHECK-NEXT: entry:
|
|
// CHECK-NEXT: [[RETVAL:%.*]] = alloca i32, align 4
|
|
// CHECK-NEXT: store i32 0, i32* [[RETVAL]], align 4
|
|
// CHECK-NEXT: call void @llvm.clear_cache(i8* getelementptr inbounds ([32 x i8], [32 x i8]* @buffer, i64 0, i64 0), i8* getelementptr inbounds ([32 x i8], [32 x i8]* @buffer, i64 1, i64 0))
|
|
// CHECK-NEXT: ret i32 0
|
|
//
|
|
int main(void) {
|
|
__builtin___clear_cache(buffer, buffer+32);
|
|
return 0;
|
|
}
|