Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
gcc 10 build times
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Mon Mar 08, 2021 2:05 am    Post subject: gcc 10 build times Reply with quote

34 minutes on a Ryzen 2700X
4 hours 23 minutes on AMD A8-7600 (Bulldozer core)

Phenom II & Athlon II X3, can't bear to think about it. I have a fam10 build environment on the Ryzen 2700X. building gcc10 as a package (--buildpkgonly) for fam10 on the Ryzen right now.
EDIT:
33 minutes 52 seconds on Ryzen building for fam10


Last edited by Tony0945 on Mon Mar 08, 2021 3:56 am; edited 1 time in total
Back to top
View user's profile Send private message
mike155
Advocate
Advocate


Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany

PostPosted: Mon Mar 08, 2021 2:16 am    Post subject: Reply with quote

Quote:
4 hours 23 minutes on AMD A8-7600 (Bulldozer core)

That seems to be way too long! Excessive swapping?

Please post the output of 'emerge --info gcc' on that machine.
Back to top
View user's profile Send private message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Mon Mar 08, 2021 3:15 am    Post subject: Reply with quote

mike155 wrote:
Please post the output of 'emerge --info gcc' on that machine.
https://dpaste.com/EREKCX7KB
Back to top
View user's profile Send private message
sdauth
Guru
Guru


Joined: 19 Sep 2018
Posts: 569
Location: Ásgarðr

PostPosted: Mon Mar 08, 2021 3:39 am    Post subject: Reply with quote

On a AMD A10-6800K APU :

Tue Feb 23 19:51:22 2021 >>> sys-devel/gcc-10.2.0-r5
merge time: 4 hours, 31 minutes and 33 seconds.

No overclock, 1600MHz ram, nothing running in parallel. I trashed the log for GCC9 but I remember being more like 3h50min or something.
Both with fortran, graphite, hardened, lto, pgo enabled.

Nothing so terrible to be honest. On my Atom, we would be speaking in days.
That Ryzen build time for GCC makes me jealous though but now is not really the right time to build a new PC. :o Especially in the GPU area.
Back to top
View user's profile Send private message
saellaven
l33t
l33t


Joined: 23 Jul 2006
Posts: 646

PostPosted: Mon Mar 08, 2021 4:28 am    Post subject: Reply with quote

Ryzen 3700X:

Machine A:
Sun Mar 7 23:24:02 2021 >>> sys-devel/gcc-10.2.0-r5
merge time: 22 minutes and 45 seconds.

Machine B:
Sun Mar 7 23:24:07 2021 >>> sys-devel/gcc-10.2.0-r5
merge time: 22 minutes and 44 seconds.
_________________
Ryzen 3700X, Asus Prime X570-Pro, 64 GB DDR4 3200, GeForce GTX 1660 Super
openrc-0.17, ~vanilla-sources, ~nvidia-drivers, ~gcc
Back to top
View user's profile Send private message
Anon-E-moose
Watchman
Watchman


Joined: 23 May 2008
Posts: 6097
Location: Dallas area

PostPosted: Mon Mar 08, 2021 11:08 am    Post subject: Reply with quote

I had put off building gcc 10, I just didn't want to mess with it, but lately I've been thinking about upgrading, and was curious as to how much slower that 9.3.
The answer seems to be not much, 9.3 ~ 20 min and from saellaven's posts, I'll spend a couple of minutes more. Good.
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland
Back to top
View user's profile Send private message
Irre
Guru
Guru


Joined: 09 Nov 2013
Posts: 434
Location: Stockholm

PostPosted: Mon Mar 08, 2021 1:18 pm    Post subject: Reply with quote

Earlier GCCs seem to be faster.
Code:
     Mon Feb 25 11:26:13 2019 >>> sys-devel/gcc-8.3.0
       merge time: 1 hour, 38 minutes and 6 seconds.

     Tue Apr  9 09:22:13 2019 >>> sys-devel/gcc-8.3.0-r1
       merge time: 1 hour, 43 minutes and 2 seconds.

     Mon May  6 12:24:47 2019 >>> sys-devel/gcc-9.1.0
       merge time: 1 hour, 50 minutes and 9 seconds.

     Fri Nov 29 17:42:04 2019 >>> sys-devel/gcc-9.2.0-r2
       merge time: 1 hour, 48 minutes and 1 second.

     Sun Dec  8 13:09:05 2019 >>> sys-devel/gcc-9.2.0-r2
       merge time: 2 hours, 1 minute and 11 seconds.

     Tue Jan 14 01:25:37 2020 >>> sys-devel/gcc-10.0.0_pre9999
       merge time: 2 hours, 19 minutes and 6 seconds.

     Sun Mar 15 11:17:10 2020 >>> sys-devel/gcc-9.2.0-r2
       merge time: 2 hours and 32 seconds.

     Wed May  6 12:14:26 2020 >>> sys-devel/gcc-9.3.0
       merge time: 2 hours, 4 minutes and 13 seconds.

     Thu Feb 11 14:18:37 2021 >>> sys-devel/gcc-10.2.0-r5 (lto)
       merge time: 13 hours, 19 minutes and 30 seconds.

     Thu Mar  4 07:28:30 2021 >>> sys-devel/gcc-10.2.0-r5 (-lto)
       merge time: 5 hours, 54 minutes and 38 seconds.

No swapping was needed. New compiler is really slow, but I hope it generates better code.
Back to top
View user's profile Send private message
mike155
Advocate
Advocate


Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany

PostPosted: Mon Mar 08, 2021 1:32 pm    Post subject: Reply with quote

Tony0945 wrote:
mike155 wrote:
Please post the output of 'emerge --info gcc' on that machine.
https://dpaste.com/EREKCX7KB

Thanks for the data. Your output
Code:
KiB Mem:    15382324 total,   6029332 free
CFLAGS="-march=native -O2 -pipe"
MAKEOPTS="-j4"

doesn't look like excessive swapping - unless a huge amount of your RAM was used by other programs or by tmpfs or RAM disks...

4 hours is too long. My desktop machine has an Intel Core i5-3570K CPU (4 cores, launched in 2012), which should be similar to your CPU. Emerging GCC takes 56 minutes. I can't believe that your AMD A8-7600 is so much slower. Something is wrong on your machine.
Back to top
View user's profile Send private message
mike155
Advocate
Advocate


Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany

PostPosted: Mon Mar 08, 2021 1:41 pm    Post subject: Reply with quote

Irre wrote:
Earlier GCCs seem to be faster.
Code:
     Mon Feb 25 11:26:13 2019 >>> sys-devel/gcc-8.3.0
       merge time: 1 hour, 38 minutes and 6 seconds.

     Tue Apr  9 09:22:13 2019 >>> sys-devel/gcc-8.3.0-r1
       merge time: 1 hour, 43 minutes and 2 seconds.

     Mon May  6 12:24:47 2019 >>> sys-devel/gcc-9.1.0
       merge time: 1 hour, 50 minutes and 9 seconds.

     Fri Nov 29 17:42:04 2019 >>> sys-devel/gcc-9.2.0-r2
       merge time: 1 hour, 48 minutes and 1 second.

     Sun Dec  8 13:09:05 2019 >>> sys-devel/gcc-9.2.0-r2
       merge time: 2 hours, 1 minute and 11 seconds.

     Tue Jan 14 01:25:37 2020 >>> sys-devel/gcc-10.0.0_pre9999
       merge time: 2 hours, 19 minutes and 6 seconds.

     Sun Mar 15 11:17:10 2020 >>> sys-devel/gcc-9.2.0-r2
       merge time: 2 hours and 32 seconds.

     Wed May  6 12:14:26 2020 >>> sys-devel/gcc-9.3.0
       merge time: 2 hours, 4 minutes and 13 seconds.

     Thu Feb 11 14:18:37 2021 >>> sys-devel/gcc-10.2.0-r5 (lto)
       merge time: 13 hours, 19 minutes and 30 seconds.

     Thu Mar  4 07:28:30 2021 >>> sys-devel/gcc-10.2.0-r5 (-lto)
       merge time: 5 hours, 54 minutes and 38 seconds.

No swapping was needed. New compiler is really slow, but I hope it generates better code.

I can't believe those numbers. It's true that more time is needed to compile GCC 10 - but only a few percent! Below are the results on my 8-year-old server (4 cores):
Code:
2019-05-07T20:33:34 >>> sys-devel/gcc-8.3.0-r1:  36′57″
2019-11-09T00:14:57 >>> sys-devel/gcc-9.2.0-r2:  48′01″
2020-04-19T14:33:09 >>> sys-devel/gcc-9.3.0:     45′22″
2020-07-09T22:22:22 >>> sys-devel/gcc-9.3.0-r1:  51′24″
2020-07-10T00:03:01 >>> sys-devel/gcc-10.1.0-r2: 50′51″
2021-03-08T02:25:49 >>> sys-devel/gcc-10.2.0-r5: 48′04″
Back to top
View user's profile Send private message
apiaio
Guru
Guru


Joined: 04 Dec 2008
Posts: 417

PostPosted: Mon Mar 08, 2021 3:08 pm    Post subject: Reply with quote

Code:
genlop -t gcc
 * sys-devel/gcc

     Sun Apr  5 18:39:10 2020 >>> sys-devel/gcc-9.2.0-r2
       merge time: 37 minutes and 50 seconds.

     Sat Apr 18 21:11:40 2020 >>> sys-devel/gcc-9.3.0
       merge time: 36 minutes and 31 seconds.

     Sun Jul 12 18:17:00 2020 >>> sys-devel/gcc-9.3.0-r1
       merge time: 37 minutes and 26 seconds.

     Fri Dec 18 19:19:14 2020 >>> sys-devel/gcc-9.3.0-r2
       merge time: 37 minutes and 29 seconds.

     Sun Mar  7 18:27:59 2021 >>> sys-devel/gcc-10.2.0-r5
       merge time: 38 minutes and 26 seconds.

i7, 16 GB OM, SSD
Back to top
View user's profile Send private message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Mon Mar 08, 2021 3:13 pm    Post subject: Reply with quote

Anon-E-moose wrote:
I had put off building gcc 10, I just didn't want to mess with it,

It turned stable, so it showed up to be built. However, I have gcc-config to use 9.3.0 and added gcc:9.3.0 to world.
The last thing I need is a slow compiler. Also the initial bug reports. I'm afraid GCC is sacrificing quality for new and shiny.
Some intel CPU's were added to march, so people with those CPU's might want to switch right away.
Phoronix has a comparison of performance on Intel's https://www.phoronix.com/scan.php?page=article&item=gcc5-gcc10-benchmarks&num=1
Maybe he'll do one on AMD
Back to top
View user's profile Send private message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Mon Mar 08, 2021 3:28 pm    Post subject: Reply with quote

Code:
~ $ genlop -t gcc
 * sys-devel/gcc

     Sun Sep 20 13:10:57 2020 >>> sys-devel/gcc-9.3.0-r1
       merge time: 35 minutes and 30 seconds.

     Sun Sep 20 13:41:03 2020 >>> sys-devel/gcc-8.4.0-r1
       merge time: 30 minutes and 6 seconds.

     Mon Dec 28 14:23:37 2020 >>> sys-devel/gcc-9.3.0-r2
       merge time: 34 minutes and 23 seconds.

     Sun Feb  7 09:40:46 2021 >>> sys-devel/gcc-8.4.0-r2
       merge time: 28 minutes and 30 seconds.

     Sun Mar  7 17:53:00 2021 >>> sys-devel/gcc-10.2.0-r5
       merge time: 33 minutes and 55 seconds.
That's from the 2700X. Actually built faster than 9.3.0
9.3.0 builds were under Mate and the 10.2.0 under Openbox

8.4.0 definitely faster.
Back to top
View user's profile Send private message
figueroa
Advocate
Advocate


Joined: 14 Aug 2005
Posts: 2961
Location: Edge of marsh USA

PostPosted: Mon Mar 08, 2021 7:54 pm    Post subject: Reply with quote

I just got 62 minutes for my Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz w/16GB RAM, amd64, -j9

Also, 126 minutes for the AMD Phenom(tm) 8650 Triple-Core Processor w/8GB RAM, x86, -j4

I've gone ahead and converted both systems to 10.2.0.

On the x86 box, I've got build time stats back to 2004:
Code:
# genlop -t gcc
 * sys-devel/gcc

     Wed Oct 27 18:38:45 2004 >>> sys-devel/gcc-3.3.4-r1
       merge time: 8 seconds.

     Wed Oct 27 18:47:15 2004 >>> sys-devel/gcc-3.3.4-r1
       merge time: 7 seconds.

     Fri Dec  3 13:18:55 2004 >>> sys-devel/gcc-3.3.4-r1
       merge time: 17 minutes and 58 seconds.

     Wed Jan 12 16:29:26 2005 >>> sys-devel/gcc-3.3.5-r1
       merge time: 29 minutes and 23 seconds.

     Mon Apr 11 18:11:09 2005 >>> sys-devel/gcc-3.3.5.20050130-r1
       merge time: 21 minutes and 13 seconds.

     Tue Sep 13 10:38:08 2005 >>> sys-devel/gcc-3.3.6
       merge time: 25 minutes and 25 seconds.

     Sat Dec  3 09:17:28 2005 >>> sys-devel/gcc-3.4.4-r1
       merge time: 28 minutes and 8 seconds.

     Thu Mar  2 01:03:21 2006 >>> sys-devel/gcc-3.4.5
       merge time: 28 minutes and 45 seconds.

     Thu Mar 30 21:41:53 2006 >>> sys-devel/gcc-3.4.5-r1
       merge time: 25 minutes and 54 seconds.

     Fri Jun  9 11:04:57 2006 >>> sys-devel/gcc-3.4.6-r1
       merge time: 28 minutes and 27 seconds.

     Fri Sep 15 09:58:28 2006 >>> sys-devel/gcc-4.1.1
       merge time: 1 hour, 14 minutes and 56 seconds.

     Tue Sep 26 23:14:08 2006 >>> sys-devel/gcc-4.1.1
       merge time: 56 minutes and 13 seconds.

     Wed Sep 27 03:59:56 2006 >>> sys-devel/gcc-4.1.1
       merge time: 56 minutes and 50 seconds.

     Wed Nov 15 10:10:46 2006 >>> sys-devel/gcc-4.1.1-r1
       merge time: 1 hour, 3 minutes and 25 seconds.

     Sun Jan 21 11:52:07 2007 >>> sys-devel/gcc-4.1.1-r3
       merge time: 52 minutes and 24 seconds.

     Sun May 20 11:00:38 2007 >>> sys-devel/gcc-4.1.2
       merge time: 57 minutes and 30 seconds.

     Fri Jun 27 13:07:52 2008 >>> sys-devel/gcc-4.1.2
       merge time: 1 hour, 15 minutes and 16 seconds.

     Sat May 30 11:41:55 2009 >>> sys-devel/gcc-4.3.2-r3
       merge time: 26 minutes and 48 seconds.

     Sat Jul  4 10:15:26 2009 >>> sys-devel/gcc-4.3.2-r3
       merge time: 20 minutes and 9 seconds.

     Sat Oct 17 10:41:36 2009 >>> sys-devel/gcc-4.3.4
       merge time: 23 minutes and 56 seconds.

     Mon Oct 19 15:49:32 2009 >>> sys-devel/gcc-4.3.4
       merge time: 18 minutes and 3 seconds.

     Tue Oct 20 09:54:37 2009 >>> sys-devel/gcc-4.3.4
       merge time: 17 minutes and 46 seconds.

     Mon Jan 11 13:35:18 2010 >>> sys-devel/gcc-4.3.4
       merge time: 19 minutes and 2 seconds.

     Sun Jun  6 20:34:58 2010 >>> sys-devel/gcc-4.4.3-r2
       merge time: 19 minutes and 9 seconds.

     Sat Nov 20 16:57:33 2010 >>> sys-devel/gcc-4.4.4-r2
       merge time: 18 minutes and 47 seconds.

     Sat Nov 20 20:40:37 2010 >>> sys-devel/gcc-4.4.4-r2
       merge time: 14 minutes and 49 seconds.

     Mon Nov 22 01:33:47 2010 >>> sys-devel/gcc-4.4.4-r2
       merge time: 14 minutes and 53 seconds.

     Wed Mar 23 22:43:40 2011 >>> sys-devel/gcc-4.4.4-r2
       merge time: 19 minutes and 26 seconds.

     Mon Sep  5 12:56:25 2011 >>> sys-devel/gcc-4.4.4-r2
       merge time: 15 minutes and 26 seconds.

     Tue Nov 15 13:06:41 2011 >>> sys-devel/gcc-4.4.4-r2
       merge time: 15 minutes and 45 seconds.

     Sat Mar  3 14:33:46 2012 >>> sys-devel/gcc-4.5.3-r2
       merge time: 20 minutes and 52 seconds.

     Wed Oct  3 13:30:52 2012 >>> sys-devel/gcc-4.5.4
       merge time: 22 minutes and 9 seconds.

     Fri Nov 23 13:16:57 2012 >>> sys-devel/gcc-4.5.4
       merge time: 20 minutes and 23 seconds.

     Fri Jan 11 10:34:08 2013 >>> sys-devel/gcc-4.6.3
       merge time: 22 minutes and 27 seconds.

     Tue Jan 15 16:30:46 2013 >>> sys-devel/gcc-4.6.3
       merge time: 22 minutes and 26 seconds.

     Thu Jan 24 11:11:36 2013 >>> sys-devel/gcc-4.6.3
       merge time: 21 minutes and 55 seconds.

     Tue Jan 29 19:39:40 2013 >>> sys-devel/gcc-4.6.3
       merge time: 21 minutes and 3 seconds.

     Tue Feb 19 18:30:58 2013 >>> sys-devel/gcc-4.6.3
       merge time: 21 minutes and 56 seconds.

     Tue Feb 19 18:50:46 2013 >>> sys-devel/gcc-4.5.4
       merge time: 19 minutes and 48 seconds.

     Fri May 17 13:43:05 2013 >>> sys-devel/gcc-4.6.3
       merge time: 19 minutes and 34 seconds.

     Tue Oct  8 14:12:53 2013 >>> sys-devel/gcc-4.7.3-r1
       merge time: 29 minutes and 39 seconds.

     Thu Dec 26 13:55:57 2013 >>> sys-devel/gcc-4.7.3-r1
       merge time: 31 minutes and 6 seconds.

     Tue Jan 21 14:23:40 2014 >>> sys-devel/gcc-4.7.3-r1
       merge time: 31 minutes and 23 seconds.

     Wed Nov  5 17:37:46 2014 >>> sys-devel/gcc-4.8.3
       merge time: 33 minutes and 1 second.

     Sat Apr 18 15:48:42 2015 >>> sys-devel/gcc-4.8.4
       merge time: 31 minutes and 26 seconds.

     Mon Jun  1 18:41:00 2015 >>> sys-devel/gcc-4.8.4
       merge time: 31 minutes and 18 seconds.

     Thu Sep 24 00:21:17 2015 >>> sys-devel/gcc-4.8.5
       merge time: 31 minutes and 18 seconds.

     Sat Oct 24 10:33:38 2015 >>> sys-devel/gcc-4.9.3
       merge time: 34 minutes and 38 seconds.

     Mon Feb 15 12:55:03 2016 >>> sys-devel/gcc-4.9.3
       merge time: 42 minutes and 42 seconds.

     Mon May  9 12:59:04 2016 >>> sys-devel/gcc-4.9.3
       merge time: 46 minutes and 20 seconds.

     Wed Jun 22 18:56:01 2016 >>> sys-devel/gcc-4.9.3
       merge time: 45 minutes and 42 seconds.

     Thu Dec 22 15:52:10 2016 >>> sys-devel/gcc-4.9.4
       merge time: 45 minutes and 11 seconds.

     Wed Apr 19 15:42:37 2017 >>> sys-devel/gcc-5.4.0-r3
       merge time: 58 minutes and 40 seconds.

     Thu Apr 20 13:58:37 2017 >>> sys-devel/gcc-5.4.0-r3
       merge time: 58 minutes and 9 seconds.

     Mon Sep 25 13:51:14 2017 >>> sys-devel/gcc-5.4.0-r3
       merge time: 1 hour, 12 minutes and 59 seconds.

     Mon Nov 20 15:27:57 2017 >>> sys-devel/gcc-6.4.0
       merge time: 1 hour, 12 minutes and 25 seconds.

     Fri Dec  1 00:39:35 2017 >>> sys-devel/gcc-6.4.0
       merge time: 1 hour, 14 minutes and 24 seconds.

     Fri Jan 12 12:29:30 2018 >>> sys-devel/gcc-6.4.0-r1
       merge time: 1 hour, 11 minutes and 59 seconds.

     Thu Apr 26 14:43:14 2018 >>> sys-devel/gcc-6.4.0-r1
       merge time: 1 hour, 12 minutes and 31 seconds.

     Fri Apr 27 22:26:43 2018 >>> sys-devel/gcc-6.4.0-r1
       merge time: 1 hour, 12 minutes and 22 seconds.

     Wed Jun 20 19:50:06 2018 >>> sys-devel/gcc-7.3.0-r3
       merge time: 1 hour, 18 minutes and 27 seconds.

     Fri Jul  6 21:07:17 2018 >>> sys-devel/gcc-7.3.0-r3
       merge time: 1 hour, 19 minutes and 25 seconds.

     Sat Jul  7 23:59:07 2018 >>> sys-devel/gcc-7.3.0-r3
       merge time: 1 hour, 19 minutes and 29 seconds.

     Mon Feb 25 16:28:01 2019 >>> sys-devel/gcc-8.2.0-r6
       merge time: 1 hour, 39 minutes and 31 seconds.

     Mon May 13 15:11:01 2019 >>> sys-devel/gcc-8.3.0-r1
       merge time: 1 hour, 42 minutes and 44 seconds.

     Tue Nov  5 14:46:51 2019 >>> sys-devel/gcc-8.3.0-r1
       merge time: 1 hour, 40 minutes and 29 seconds.

     Fri Nov  8 15:33:46 2019 >>> sys-devel/gcc-9.2.0-r2
       merge time: 1 hour, 59 minutes and 31 seconds.

     Mon Apr 20 16:27:29 2020 >>> sys-devel/gcc-9.3.0
       merge time: 2 hours and 11 seconds.

     Thu Jul  9 16:40:13 2020 >>> sys-devel/gcc-9.3.0-r1
       merge time: 2 hours and 2 seconds.

     Sun Dec  6 11:46:57 2020 >>> sys-devel/gcc-9.3.0-r2
       merge time: 2 hours and 31 seconds.

     Mon Mar  8 13:55:57 2021 >>> sys-devel/gcc-10.2.0-r5
       merge time: 2 hours, 5 minutes and 51 secon

_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Wed Mar 10, 2021 7:09 am    Post subject: Reply with quote

my results are contaminated with distcc so take with grain of salt, along with tmpfs and running (mostly idle) VM's at the same time. Also machines are distcc'ing each other so that will slow things down...

Also I may have disabled mitigations, with exception of the Atom of course.

"?" means still pending. Atom and P4 are 1C2T, i5 is 2C4T, i7 is 4C8T. I did not load down all 8 threads. All are amd64 except Atom and c2q32/4g. i5/i7 are SSD'd
None of the machines are overclocked currently. i7=~3.5GHz+TB, i5=~1.7GHz+TB, P4=3.4GHz, C2 machines are all around 2.7GHz, Atom is 1.6GHz

Code:
           i7/8g   c2q/8g c2q/4g c2d/4g  Atom/2g P4/3g  i5/8g c2q32/4g
gcc10        58m     2h8m  2h20m  3h46m     ?       ?    3h8m   1h41m
gcc9         51m    1h41m     ?   3h30m   12h      8h   2h17m   1h39m
rust1.47   1h20m    2h31m  2h39m  4h54m   28h     11h   4h43m   3h15m


... continuing to fill out the table as data comes in...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?


Last edited by eccerr0r on Fri Mar 12, 2021 3:37 am; edited 5 times in total
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3267
Location: Canada

PostPosted: Wed Mar 10, 2021 7:53 am    Post subject: Re: gcc 10 build times Reply with quote

Tony0945 wrote:
34 minutes on a Ryzen 2700X
4 hours 23 minutes on AMD A8-7600 (Bulldozer core)

Phenom II & Athlon II X3, can't bear to think about it. I have a fam10 build environment on the Ryzen 2700X. building gcc10 as a package (--buildpkgonly) for fam10 on the Ryzen right now.
EDIT:
33 minutes 52 seconds on Ryzen building for fam10



Hm 2007 intel core2 duo, 2GHZ, 4Gb RAM, 169 minutes = 2 hours, 49 minutes

2017 intel i7 3.8 GHz, 4 cores ( but -j3), 16 Gb RAM, 79 minutes
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Wed Mar 10, 2021 8:12 am    Post subject: Re: gcc 10 build times Reply with quote

dmpogo wrote:
Hm 2007 intel core2 duo, 2GHZ, 4Gb RAM, 169 minutes = 2 hours, 49 minutes

What kind of c2d is it? Wondering why my c2d and c2qs (all around 2.7GHz, all have at least 4GB RAM) are so slow? They are all on rust spinners. Then again they are taking distccd jobs and doing mythbackend/qemu work...)?
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
Anon-E-moose
Watchman
Watchman


Joined: 23 May 2008
Posts: 6097
Location: Dallas area

PostPosted: Wed Mar 10, 2021 10:02 am    Post subject: Re: gcc 10 build times Reply with quote

eccerr0r wrote:
dmpogo wrote:
Hm 2007 intel core2 duo, 2GHZ, 4Gb RAM, 169 minutes = 2 hours, 49 minutes

What kind of c2d is it? Wondering why my c2d and c2qs (all around 2.7GHz, all have at least 4GB RAM) are so slow? They are all on rust spinners. Then again they are taking distccd jobs and doing mythbackend/qemu work...)?


swapping ???
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Wed Mar 10, 2021 4:20 pm    Post subject: Reply with quote

Don't think it's swapping, the numbers seem quite consistent depending on clock and core count...

Then again the -j -l counts technically should be different for gcc/rust compared to other packages; even worse, should be different for stage1/0 than the other stages.

---

For curiosity's sake I disabled distcc and set MAKEOPTS to more reasonable numbers just in case it was swapping.
It looks like my c2d/4g got through stage1 in only 33 minutes. This is corresponding to a 100 minute build time which is a lot faster than with distcc options - so it looks like I will need to make an env for gcc and probably rust as well to optimize for these packages.

If it really can finish in 100 minutes, then I have to fix all my machines... distcc options for gcc is BAD.

---

Nope, not 100 minutes. It took 3h20m this time with -j3 (c2d@2.66/4g).
Stage1 33 min
Stage2 92 min
Stage3 remainder...
Also this will be a multilib gcc, wonder how much this adds to build time...

Oh... gfortran... I'm building this... What USE flags are people using?

(Added for reference for this c2d/4g: )
[ebuild R ] sys-devel/gcc-10.2.0-r5:10::gentoo USE="(cxx) fortran (multilib) nls nptl openmp pch (pie) sanitize ssp (-ada) -d -debug -doc (-fixed-point) -go -graphite (-hardened) -jit (-libssp) -lto -objc -objc++ -objc-gc -pgo -systemtap -test -vanilla -vtv -zstd" 0 KiB
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?


Last edited by eccerr0r on Wed Mar 10, 2021 11:24 pm; edited 1 time in total
Back to top
View user's profile Send private message
saellaven
l33t
l33t


Joined: 23 Jul 2006
Posts: 646

PostPosted: Wed Mar 10, 2021 11:13 pm    Post subject: Reply with quote

eccerr0r wrote:

Oh... gfortran... I'm building this... What USE flags are people using?


[ebuild R ] sys-devel/gcc-10.2.0-r5:10::gentoo USE="(cxx) fortran graphite (multilib) nls nptl openmp pch (pie) sanitize ssp (-ada) -d -debug -doc (-fixed-point) -go (-hardened) -jit (-libssp) -lto -objc -objc++ -objc-gc -pgo -systemtap -test -vanilla -vtv -zstd" 0 KiB
_________________
Ryzen 3700X, Asus Prime X570-Pro, 64 GB DDR4 3200, GeForce GTX 1660 Super
openrc-0.17, ~vanilla-sources, ~nvidia-drivers, ~gcc
Back to top
View user's profile Send private message
psycho
Guru
Guru


Joined: 22 Jun 2007
Posts: 534
Location: New Zealand

PostPosted: Thu Mar 11, 2021 12:24 am    Post subject: Reply with quote

64 minutes here on this old i5-3470 (8G RAM, no swap, old spinning hard disks).
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Thu Mar 11, 2021 12:27 am    Post subject: Reply with quote

Same USE flags, but only using local resources (no distcc):

My c2d(2.67GHz)/4g got 3h20m, my i5(1.7GHz+TB)/8g got 3h8m. Seems turboboost and microarchitectural speedups were able to make up for the lower minspeed of the i5. Both are dual core processors though the i5 has 4 threads (and SSD) while the c2d has 2 (rust spinner).

I still would like to know how a 2GHz c2d was able to get 2h49m... If it were omitting fortran, that would explain things among other possibilities.

---

I found a 2.4GHz c2q only needed 1h40m to complete gcc10. This c2q is 32-bit however, this may also be part of the reason for why this machine is finishing faster than the other core2 machines.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3267
Location: Canada

PostPosted: Fri Mar 12, 2021 4:04 am    Post subject: Re: gcc 10 build times Reply with quote

eccerr0r wrote:
dmpogo wrote:
Hm 2007 intel core2 duo, 2GHZ, 4Gb RAM, 169 minutes = 2 hours, 49 minutes

What kind of c2d is it? Wondering why my c2d and c2qs (all around 2.7GHz, all have at least 4GB RAM) are so slow? They are all on rust spinners. Then again they are taking distccd jobs and doing mythbackend/qemu work...)?


Code:

processor        :0
.......

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
stepping        : 11
microcode       : 0xb3
cpu MHz         : 2063.026
cache size      : 4096 KB
.....


I have misstype 2.66 GHz, of course

And I did compile it on external eSATA rotating disk for build space - did not fit in 2 GB ramdisk, as previous versions did :(
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Fri Mar 12, 2021 6:40 am    Post subject: Re: gcc 10 build times Reply with quote

dmpogo wrote:
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz

Are you running 32 or 64 bit?

I just found that a 32-bit install is in the ballpark of the number you got... the numbers I'm getting would make more sense (possibly) this way unless something magical is really happening with that one specific c2q (it's less MHz but finished gcc10 faster - only 100 minutes) too...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 3267
Location: Canada

PostPosted: Fri Mar 12, 2021 8:06 am    Post subject: Re: gcc 10 build times Reply with quote

eccerr0r wrote:
dmpogo wrote:
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz

Are you running 32 or 64 bit?

I just found that a 32-bit install is in the ballpark of the number you got... the numbers I'm getting would make more sense (possibly) this way unless something magical is really happening with that one specific c2q (it's less MHz but finished gcc10 faster - only 100 minutes) too...



64 bit, and I have fortran - I use it.

Code:

equery uses gcc

 * Found these USE flags for sys-devel/gcc-10.2.0-r5:
 U I
 - - d             : Enable support for the D programming language
 - - debug     : Enable extra debug codepaths, like asserts and extra output. If you want to get
                       meaningful backtraces see
                       https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 - - doc         : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package
                      instead of globally
 + + fortran   : Add support for fortran
 - - go           : Build the GCC Go language frontend.
 - - graphite  : Add support for the framework for loop optimizations based on a polyhedral intermediate
                       representation
 - - jit            : Enable libgccjit so other applications can embed gcc for Just-In-Time compilation. This
                      will slow down the compiler a bit as it forces all of the toolchain to be shared libs.
 - - lto           : Build using Link Time Optimizations (LTO)
 + + nls        : Add Native Language Support (using gettext - GNU locale utilities)
 + + nptl       : Enable support for Native POSIX Threads Library, the new threading module (requires
                      linux-2.6 or better usually)
 - - objc        : Build support for the Objective C code language
 - - objc++    : Build support for the Objective C++ language
 - - objc-gc   : Build support for the Objective C code language Garbage Collector
 + + openmp    : Build support for the OpenMP (support parallel computing), requires >=sys-devel/gcc-4.2
                          built with USE="openmp"
 + + pch       : Enable precompiled header support for faster compilation at the expense of disk space
                      and memory (>=sys-devel/gcc-3.4 only)
 - - pgo       : Build GCC using Profile Guided Optimization (PGO)
 + + sanitize  : Build support for various sanitizer functions (ASAN/TSAN/etc...)
 + + ssp         : Build packages with stack smashing protector on by default
 - - systemtap : enable systemtap static probe points
 - - test          : Enable dependencies and/or preparations necessary to run tests (usually controlled by
                       FEATURES=test but can be toggled independently)
 - - vanilla      : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL
                        SCALE as the severity of the meaning changes drastically
 - - vtv           : Build support for virtual table verification (a C++ hardening feature)
 - - zstd         : Enable support for ZSTD compression
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA

PostPosted: Fri Mar 12, 2021 8:38 am    Post subject: Reply with quote

USE flags match then.
Only other thing that's clearly different is kernel...

The "fast" c2q is running 4.19.86 Scaling to two cores would be in the ballpark with what you're seeing (100 mins). It's using -j6.
the "slow" c2d is running 5.4.97 (mitigations disabled) - So far the best I've seen is 3h20m with -j3 so it's still almost 20% slower.
The "slow" c2qs is running 4.14.65 and 5.4.97, both of these are close together (~130 mins). This doesn't make sense because these c2qs are clocked faster than the "fast" c2q.

Something is very wrong here, but cant put my finger on it... What's bothersome is that the rust numbers are relatively within the ballpark too based on clock frequency. Just gcc is really unexpected.

Doing the math, seems the "fast" c2q is very slow building rust relative to clock speed, so there's some other factor at hand here perhaps...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum