[10000truths]

Debug symbol size shouldn't be influencing relocation jump distances - debug info has its own ELF section.

Regardless of whether you're FAANG or not, nothing you're running should require an executable with a 2 GB large .text section. If you're bumping into that limit, then your build process likely lacks dead code elimination in the linking step. You should be using LTO for release builds. Even the traditional solution (compile your object files with -ffunction-sections and link with --gc-sections) does a good job of culling dead code at function-level granularity.

[saagarjha]

Google Chrome ships as a 500 MB binary on my machine, so if you're embedding a web browser, that's how much you need minimum. Now tack on whatever else your application needs and it's easy to see how you can go past 2 GB if you're not careful. (To be clear, I am not making a moral judgment here, I am just saying it's possible to do. Whether it should happen is a different question.)

[throwawaymobule]

Do you have some special setup?

Chromium is in the hundred and something MB range on mine last I looked. Might expand to more on install.

[yablak]

FAANGs we're deeply involved in designing LTO. See, e.g.,

https://research.google/pubs/thinlto-scalable-and-incrementa...

And other refs.

And yet...

[jeffbee]

Google also uses identical code folding. It's a pretty silly idea that a shop that big doesn't know about the compiler flags.