This is the mail archive of the
mailing list for the GCC project.
Re: Move more predefined macros
On Thu, May 16, 2002 at 08:20:57PM +0100, Neil Booth wrote:
> Zack Weinberg wrote:-
> > No target-specific code is affected. Neil, I'd like your opinion on
> > the aesthetics of the change to builtin_define_with_value; should the
> > flag parameter be two separate functions instead?
> Could that have been done with a stringification # at compile time?
> I assume version_string could be made a macro without difficulty,
> or at least a macro version provided as well?
You can't stringify the expansion of a macro in traditional C. If
__VERSION__ were never used in the code compiled by stage1/cc1, this
would be harmless; however, it is used (in toplev.c and m68hc11.c).
Therefore, we'd get bootstrap failures starting from a K+R compiler.
We could have two separate constants, version_string and
version_string_strconst, but I think that's asking for trouble.