(Well, rebuilding them with a different allocator that benchmarks well on their specific workflow.)
Make Ubuntu packages 90% faster by rebuilding them
31–40 of 375 posts
Re: Make Ubuntu packages 90% faster by rebuilding them
#32Re: Make Ubuntu packages 90% faster by rebuilding them
#33Re: Make Ubuntu packages 90% faster by rebuilding them
#34Earlier quoted context omitted.
> Are the packages all debug symbols? Upstream is stripped actually. My final build here is 43x larger than the distro binary, partly due to having plentiful debug info.
Sorry, I didn't mean symbols, I meant optimization level. Hilarious that they have symbols stripped, but still outclassed. Love to see why they wouldn't have more optimizations. I'm assuming this isn't the case for more packages? Feels too good.
Re: Make Ubuntu packages 90% faster by rebuilding them
#35Re: Make Ubuntu packages 90% faster by rebuilding them
#36Re: Make Ubuntu packages 90% faster by rebuilding them
#37Re: Make Ubuntu packages 90% faster by rebuilding them
#38> * SECURITY UPDATE: Fix multiple invalid pointer dereference, out-of-bounds write memory corruption and stack buffer overflow.
(that one was for CVE-2017-9224, CVE-2017-9226, CVE-2017-9227, CVE-2017-9228 and CVE-2017-9229)
Re: Make Ubuntu packages 90% faster by rebuilding them
#39O3 is a bad idea if the package is important. While that’s a dated opinion based on older experiences (Gentoo, various server software, etc), I suspect it’s still the easiest way to get exposed to compiler bugs.
Re: Make Ubuntu packages 90% faster by rebuilding them
#40After initial setup, it’s pretty simple and easy to use, I remember making a ton of friends at matrix’s Gentoo Linux channel, was fun times.
Fun fact, initial ChromeOS was basically just custom Gentoo Linux install, I’m not sure if they still use Gentoo Linux internally.