This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Improve vxWorks support on x86
- To: law at cygnus dot com
- Subject: Re: Improve vxWorks support on x86
- From: Zack Weinberg <zack at rabi dot columbia dot edu>
- Date: Tue, 26 Jan 1999 10:50:03 -0500
- cc: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>, egcs-patches at cygnus dot com, mrs at wrs dot com
On Tue, 26 Jan 1999 07:14:57 -0700, Jeffrey A Law wrote:
>
> In message <199901261411.PAA27302@ignucius.axis.se>you write:
> > > Date: Tue, 26 Jan 1999 06:51:50 -0700
> > > From: Jeffrey A Law <law@hurl.cygnus.com>
> >
> > > Not everything calls cpp via the gcc driver. imake for example.
> >
> > Right
> > Wouldn't TRT be to fix cccp.c:s (different) use of
> > CPP_PREDEFINES, so it applies the same -ansi magic as gcc.c?
> > (Equivalent for cpplib.)
>That would involve duplicating a lot of the spec stuff in cpp, not something
>I really want to do.
In the long run, I think it'll be simplest to prevent people from calling
cpp except via gcc. This shouldn't be hard; we dig up the shell script
someone posted a long time ago and install it as $prefix/bin/cpp. I'd send
a patch for this, but I can't find the script. It was fairly involved.
Does anyone know why the trivial
#! /bin/sh
exec gcc -E ${1+"$@"}
won't work?
zw