This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Should -dD output assertions as well as macros?
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- To: gcc at gcc dot gnu dot org
- Cc: Zack Weinberg <zack at codesourcery dot com>
- Date: Sat, 11 May 2002 20:01:38 +0100
- Subject: Should -dD output assertions as well as macros?
I think doing so would be logical. The reason I ask is
my alpha cross-compiler outputs
# 1 "/tmp/foo.c"
# 1 "<built-in>"
#define __VERSION__ "3.2 20020511 (experimental)"
#define __USER_LABEL_PREFIX__
#define __REGISTER_PREFIX__
#define __HAVE_BUILTIN_SETJMP__ 1
#define __SIZE_TYPE__ long unsigned int
#define __PTRDIFF_TYPE__ long int
#define __WCHAR_TYPE__ int
#define __WINT_TYPE__ unsigned int
#define __STDC__ 1
#define __alpha 1
#define __alpha__ 1
#define __alpha_ev4__ 1
#define __gnu_linux__ 1
#define _LONGLONG 1
#define __linux 1
#define linux 1
[...]
and the odd-looking blank lines represent built-in assertions.
*shrug* It's not important I guess.
Neil.