Comments by "Juzu Juzu" (@juzujuzu4555) on "We Should Stop Labeling Linux Distros \"Easy\" And \"Hard\"" video.
-
4
-
3
-
3
-
@pillmuncher67 Interesting, I had target as 32bit AMD too and 64 bit Intel was the compiling machine.
The issues were purely distcc related, not really crashing but just failing. It managed to get things started and then at some point just stopped using the distcc.
I thought it might be due to latency issues as I had to use wifi to connect to router.
I might try it again at some point though, because it was also about a year ago when I really tried and had motive to not give up, but I came to conclusion that it's not stable based on Gentoo IRC conversation (which I sadly don't remember the details anymore)
I'm pretty well adjusted with Gentoo ~amd64. GentooLTO overlay, beta GCC 13 with all the optimizations etc. as I'm addicted to optimization.
On that note, as I have LTO, PGO, Graphite, Ofast, all the GentooLTO things, and going from GCC 12 to GCC 13 still managed to get pretty significant speed improvements on almost all OpenSSL algorithms. 5-10% improvement on 7yo Intel laptop with 2 cores. Which I would assume should have the least improvements really from new compilers. With more cores you get improved parallelism, newer CPUs get better AVX utilization etc. but to still get so much improvement on hash etc algorithms on old Intel is pretty incredible.
I tested OpenSSL, then switched to GCC 13, compiled the same version of OpenSSL and did the testing again. So it was real reliable testing, without even restart in between the tests.
2
-
1
-
1
-
1
-
1
-
1
-
1