1*67e74705SXin Li // RUN: %clang_cc1 -triple aarch64-none-linux-gnu -fsyntax-only -verify %s 2*67e74705SXin Li // RUN: %clang_cc1 -triple aarch64-none-linux-gnu -DTEST1 -fsyntax-only -verify %s 3*67e74705SXin Li // RUN: %clang_cc1 -triple arm64-none-linux-gnu -fsyntax-only -verify %s 4*67e74705SXin Li // RUN: %clang_cc1 -triple arm64-none-linux-gnu -DTEST1 -fsyntax-only -verify %s 5*67e74705SXin Li 6*67e74705SXin Li #ifdef TEST1 7*67e74705SXin Li void __clear_cache(void *start, void *end); 8*67e74705SXin Li #endif 9*67e74705SXin Li test_clear_cache_chars(char * start,char * end)10*67e74705SXin Livoid test_clear_cache_chars(char *start, char *end) { 11*67e74705SXin Li __clear_cache(start, end); 12*67e74705SXin Li } 13*67e74705SXin Li test_clear_cache_voids(void * start,void * end)14*67e74705SXin Livoid test_clear_cache_voids(void *start, void *end) { 15*67e74705SXin Li __clear_cache(start, end); 16*67e74705SXin Li } 17*67e74705SXin Li test_clear_cache_no_args()18*67e74705SXin Livoid test_clear_cache_no_args() { 19*67e74705SXin Li // AArch32 version of this is variadic (at least syntactically). 20*67e74705SXin Li // However, on AArch64 GCC does not permit this call and the 21*67e74705SXin Li // implementation I've seen would go disastrously wrong. 22*67e74705SXin Li __clear_cache(); // expected-error {{too few arguments to function call}} 23*67e74705SXin Li } 24