This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Identifying the EGCS back-end
- To: martin at mira dot isdn dot cs dot tu-berlin dot de (Martin von Loewis)
- Subject: Re: Identifying the EGCS back-end
- From: Joe Buck <jbuck at synopsys dot com>
- Date: Fri, 6 Nov 98 9:47:35 PST
- Cc: law at cygnus dot com, peter at gerwinski dot de, egcs at cygnus dot com
> > I'm not sure of one. We have a way to identify when you're building
> > soemthing with egcs (version #s), but I don't know of a way to
> > identify when you're building gpc inside an egcs tree.
>
> Hmm. Wouldn't that be as simple as putting
>
> #define THIS_IS_EGCS
>
> into config.in, tree.h, or some like place?
Nice idea, but there's a problem, because if EGCS later becomes gcc3 it
would no longer be called EGCS.
Instead, one of these headers could give access to the gcc major and
minor version numbers: __GNUC__ and __GNUC_MINOR__ except with different
names (to represent the compiler being built rather than the compiler
being used). If the symbols are not defined, we would assume that
an older compiler is being used.