This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Overriding cc1
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Dave Korn" <dk at artimi dot com>
- Cc: "'Pat Haugen'" <pthaugen at us dot ibm dot com>, "'Ian Lance Taylor'" <ian at wasabisystems dot com>, <gcc at gcc dot gnu dot org>
- Date: 16 May 2004 02:07:10 -0300
- Subject: Re: Overriding cc1
- Organization: Red Hat Global Engineering Services Compiler Team
- References: <NUTMEGgFrYILoygXLsx00000100@NUTMEG.CAM.ARTIMI.COM>
On May 14, 2004, "Dave Korn" <dk@artimi.com> wrote:
>> -----Original Message-----
>> From: gcc-owner On Behalf Of Alexandre Oliva
>> Sent: 14 May 2004 06:49
>> On May 13, 2004, Pat Haugen <pthaugen@us.ibm.com> wrote:
>>
>> > OK, knew about -B but was hoping to just be able to
>> override cc1, which it
>> > doesn't sound like I can do.
>>
>> Well, turns out you can: just create a dir containing only a link to
>> your overrider.
> Hold on. Rather than creating lots of different versions called
> cc1.versionN, why not create lots of subdirs in ..lib/gcc-lib/$target called
> after .versionN, put the compilers in them (all still named cc1), and then
> use the -V option to make the driver choose between them?
Because nowadays -V version option re-execs gcc-version these days?
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}