[Bug other/10240] HOST_CFLAGS in gcc/Makefile.in shouldn't include XCFLAGS

["aoliva at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10240



------- Additional Comments From aoliva at gcc dot gnu dot org  2003-06-26 12:26 -------
It could be argued both ways whether XCFLAGS should be in BUILD_CFLAGS or not. 
On the one hand, XCFLAGS is used to build gen* programs when build = host, and
it might use flags that would affect the outcome of such programs (e.g., some
-DMACRO=value flag or such that would cause the gen* program to adapt its output
to limitations of the host machine, e.g., not generate functions that are too
big or so).

However, -D flags in XCFLAGS are obviated by xm_defines, which is why we don't
have XCPPFLAGS,  and since we don't have any current use of XCFLAGS, we might as
well change BUILD_CFLAGS so as to enable XCFLAGS to contain flags that are
specific to compilers for the host.

I suppose it would be fair to remove XCFLAGS from BUILD_CFLAGS now and, if
someone ever finds a need for a flag that is passed to both BUILD_CC and CC,
even when they're different, we can come up with a new name for it.

Dara, please install the obvious patch.  Bonus points for clarifying in the docs
that XCFLAGS is not used when building a compiler using a cross compiler.  Thanks,