diff options
Diffstat (limited to 'gcc/testsuite/gcc.dg/builtins-config.h')
-rw-r--r-- | gcc/testsuite/gcc.dg/builtins-config.h | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/gcc/testsuite/gcc.dg/builtins-config.h b/gcc/testsuite/gcc.dg/builtins-config.h new file mode 100644 index 00000000000..7e7d92fbaf5 --- /dev/null +++ b/gcc/testsuite/gcc.dg/builtins-config.h @@ -0,0 +1,29 @@ +/* Copyright (C) 2003 Free Software Foundation. + + Define macros useful in tests for bulitin functions. */ + +/* Define HAVE_C99_RUNTIME if the entire C99 runtime is available on + the target system. The value of HAVE_C99_RUNTIME should be the + same as the value of TARGET_C99_FUNCTIONS in the GCC machine + description. (Perhaps GCC should predefine a special macro + indicating whether or not TARGET_C99_FUNCTIONS is set, but it does + not presently do that.) */ + +#if defined(sun) +/* Solaris doesn't have the entire C99 runtime. */ +#else +/* Newlib has the "f" variants of the math functions, but not the "l" + variants. TARGET_C99_FUNCTIONS is only defined if all C99 + functions are present. Therefore, on systems using newlib, tests + of builtins will fail for both the "f" and the "l" variants, and we + should therefore not define HAVE_C99_RUNTIME. Including <ctype.h> + gives us a way of seeing if _NEWLIB_VERSION is defined. Including + <math.h> would work too, but the GLIBC math inlines cause us to + generate inferior code, which causes the test to fail, so it is + not safe to include <math.h>. */ +#include <ctype.h> +#ifdef _NEWLIB_VERSION +#else +#define HAVE_C99_RUNTIME +#endif +#endif |