This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
target-defs.h / tm.h question
- From: Kean Johnston <jkj at sco dot com>
- To: gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 05 Oct 2005 07:33:13 -0700
- Subject: target-defs.h / tm.h question
- Reply-to: jkj at sco dot com
Hi,
Is there any reason why *all* of the macros in target-defs.h
are not conditionalized? target-defs.h is always included after
tm.h, so if the target specific include sets any of the macros
that are not protected in target-defs.h, they get overwritten.
Yes, you are warned, so my question is, is the intent to only
conditioalize those macros that have actually been defined
ib the target header file and to adjust target-defs.h on a
case by case basis, or should I just clean up target-defs.h
and protect *all* of the macros from redefining what may
have been set in tm.h?
Thanks for any input.
PS. The specific case I ran into was I needed to define
TARGET_PROMOTE_FUNCTION_RETURN but target-defs.h was not
protecting its definition thereof with a #ifndef.
Kean