On Thursday, 24 July 2025 12:16:21 British Summer Time Alexandru N. Barloiu wrote: > On Thu, 2025-07-24 at 11:48 +0100, Michael wrote: > > Please post how long it takes you to emerge qtwebengine, rust, > > libreoffice. > > sorry, i dont use any of that. best i can do is: > > > > > [root@trandafira:~]# genlop -t sys-devel/gcc > * sys-devel/gcc > > Fri Jun 6 00:24:16 2025 >>> sys-devel/gcc-14.3.0 > merge time: 10 minutes and 50 seconds. > > Fri Jun 6 00:57:02 2025 >>> sys-devel/gcc-15.1.0 > merge time: 15 minutes and 24 seconds. > > > > > which is odd. and wrong. i can brag about it. but the truth is, it > should be around 20 minutes. > > > Fri Jun 6 03:08:48 2025 >>> sys-devel/gcc-15.1.0 > merge time: 22 minutes and 41 seconds. > > Sat Jun 7 12:08:11 2025 >>> sys-devel/gcc-14.3.0 > merge time: 21 minutes and 43 seconds. > > Sat Jun 7 21:46:39 2025 >>> sys-devel/gcc-15.1.0 > merge time: 22 minutes and 24 seconds. > > Sat Jun 7 22:55:58 2025 >>> sys-devel/gcc-14.3.0 > merge time: 21 minutes and 25 seconds. > > Wed Jul 9 19:01:53 2025 >>> sys-devel/gcc-15.1.1_p20250705-r1 > merge time: 22 minutes and 36 seconds. > > > with LTO on. should say. ignore the 10/15 minutes one. prolly a bug. > but gcc with lto never lies because its not about distcc. its about > your own system. those are the times. no BS times.
Thank you for this. I don't use distcc. On an AM4 MoBo with DDR4 I get 29%
slower times if I enable LTO when emerging gcc, which is to be expected.
Thu Jun 5 11:40:53 2025 >>> sys-devel/gcc-14.3.0
merge time: 17 minutes and 22 seconds.
Thu Jul 24 12:55:07 2025 >>> sys-devel/gcc-14.3.0
merge time: 24 minutes and 14 seconds.
Compared to your LTO times my PC is ~12% slower, which is surprising. I was
expecting yours would show a ~25% improvement. I wonder what performance
boost you'd get with the new AMD V-cache driver in the kernel and if this
would be realisable by a compiler. o_O
signature.asc
Description: This is a digitally signed message part.
