This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: whither specs?


> cc: gcc@gcc.gnu.org
> Date: Mon, 10 Jun 2002 13:33:30 -0400
> From: David Edelsohn <dje@watson.ibm.com>
> 
> >>>>> Geoff Keating writes:
> 
> Geoff> - Do we still want to have the 'specs' file in $(gcc_tooldir)?  It's
> Geoff> now redundant unless the user edits it, since the driver generated
> Geoff> it in the first place.  I guess the real question is, "do we want
> Geoff> to support the user changing this file?"  Is there a better way we
> Geoff> could support the functionality that people try to get by changing
> Geoff> this file?
> 
> 	Installing the specs file and having the compiler use it if it
> exists (as opposed to the internal specs), definitely helps users who need
> to tweak binary installations.  It gives users the ability to modify at
> least that part of the compiler after installation without rebuilding the
> compiler.
> 
> 	I am not saying that specs is great, but being able to fix
> something in the time it takes to edit a text file is a lot easier than
> rebuilding and reinstalling GCC.

Can you give examples of the sort of things that users might like to
change?  I'm thinking that a lot of them are along the lines of
"please pass this flag to the linker".

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]