Diving into GCC Internals
If anyone wants to make an easy but useful improvement to GCC, might I suggest: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58770
Summary: headers that use pragma once are tracked using a list resulting in slow uniqueness checks. The performance fix is to use a hash table.
Gosh, I really wish GCC had more/better documentation. Especially big picture stuff. E.g., I would like to know what register allocation algorithms it uses (and how certain details are handled), but looking at that code I noped out...
One thing I've heard about even modern compilers is that they don't really release memory during compilation, as it's faster just to use the memory and release it all when the process exits. How true is that?
Gives me PTSD to my operating systems class in university. Once upon a time I knew how a linker actually worked under the hood, but those days are long gone.
undefined
undefined
GCC really needs to get it's act together if it wants to not die. Basic things like onboarding and spectating on other people's code being reviewed is pretty hard to do from a mailing list.
GCC is already basically non-existent in academic research now, although the inner essentials of the compiler are still pretty damn good and is the benchmark for open source compilers, the stuff around the outside is suffering.
undefined