b653131345
a subprocess invocation which is pretty significant on Windows. It also likely saves a bunch of thrashing the host machine needlessly. Finally it makes the tests much more predictable and less dependent on the host. For example 'header_lookup1.c' was passing '-fno-ms-extensions' just to thwart the host detection adding it into the compilation. By runnig CC1 directly we don't have to deal with such oddities. llvm-svn: 199308
29 lines
1.2 KiB
C
29 lines
1.2 KiB
C
// RUN: %clang_cc1 -verify -fsyntax-only %s
|
|
// RUN: %clang_cc1 -emit-llvm -o %t %s
|
|
|
|
#include <stddef.h>
|
|
|
|
// Declare malloc here explicitly so we don't depend on system headers.
|
|
void * malloc(size_t) __attribute((malloc));
|
|
|
|
int no_vars __attribute((malloc)); // expected-warning {{functions returning a pointer type}}
|
|
|
|
void returns_void (void) __attribute((malloc)); // expected-warning {{functions returning a pointer type}}
|
|
int returns_int (void) __attribute((malloc)); // expected-warning {{functions returning a pointer type}}
|
|
int * returns_intptr(void) __attribute((malloc)); // no-warning
|
|
typedef int * iptr;
|
|
iptr returns_iptr (void) __attribute((malloc)); // no-warning
|
|
|
|
__attribute((malloc)) void *(*f)(); // expected-warning{{'malloc' attribute only applies to functions returning a pointer type}}
|
|
__attribute((malloc)) int (*g)(); // expected-warning{{'malloc' attribute only applies to functions returning a pointer type}}
|
|
|
|
__attribute((malloc))
|
|
void * xalloc(unsigned n) { return malloc(n); } // no-warning
|
|
// RUN: grep 'define noalias .* @xalloc(' %t
|
|
|
|
#define malloc_like __attribute((__malloc__))
|
|
void * xalloc2(unsigned) malloc_like;
|
|
void * xalloc2(unsigned n) { return malloc(n); }
|
|
// RUN: grep 'define noalias .* @xalloc2(' %t
|
|
|