What makes a difference in the resulting compiler's speed when building gcc?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: gcc-help@xxxxxxxxxxx
- Subject: What makes a difference in the resulting compiler's speed when building gcc?
- From: "Sven C. Dack" <sven.c.dack@xxxxxxx>
- Date: Thu, 27 Oct 2016 16:53:35 +0100
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0
Hello,
I've been installing private copies of gcc for a while now, but only recently
did I notice that my distro's gcc (Debian testing) is doing much better when
comparing compile times than any of my copies. For instance does it take 230s
for my copy to compile a linux kernel, but only 163s for my distro's gcc, which
is almost a minute in difference for something that doesn't take more than 3-4
minutes to compile.
What makes this noteworthy for me is that I've compiled my copy with
profiledbootstrap and LTO enabled and also optimized it for my CPU, whereas the
distro's compiler won't have been optimized quite that much, but yet is it so
much faster in speed. I don't know how exactly my distro's gcc has been set up,
because the Debian build rules are rather complex and include their own set of
patches. So I thought I start with asking here first.
What is that can make such a huge difference in compile speed for two copies of
gcc, both version 6.2, using the same options, on the same source? Or are any of
the configure options know to have a huge impact on the resulting compiler's speed?
Sven
[Index of Archives]
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]