This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Compile time in Windows
- From: Ian Lance Taylor <ian at airs dot com>
- To: "Jeff Baker" <jbaker at qnx dot com>
- Cc: <binutils at sources dot redhat dot com>
- Date: 05 May 2003 17:57:09 -0700
- Subject: Re: Compile time in Windows
- References: <000501c31317$f57a3bb0$0601040a@jbaker1200>
"Jeff Baker" <jbaker@qnx.com> writes:
> I know this question is somewhat vague, but that's how it was presented to
> me so that's what I have to start with. I've been asked to find a way to
> make gcc and the binutils faster in Windows ( Cygwin ). Before I get down
> to the level of profiling the code I thought I'd ask if there are any
> compile time options I may not be aware of that might speed the works up a
> little.
Cygwin introduces quite a bit of latency, and Windows is slow to start
with.
If you want to spend a fair amount of time on this, I would advise
developing a true Windows port of the tools, rather than using Cygwin.
The mingw32 stuff might help here--I haven't looked at it in a while.
You should plan carefully, and probably consult with the developers,
in order to get your patches back into the mainline cleanly.
Other than that well-understood inefficiency, there aren't any compile
time options which will help you. We'd all like to use the gcc
-frun-faster option, but unfortunately it hasn't been implemented yet.
There may well be slow spots in the code which profiling will uncover,
and I encourage you to use it.
Ian