kind of expected gcc to see right through the 300 gigs of code and compile it down to the tenish instructions.
> disabling optimizations with /Od
And that weird flag is because it's a windows compiler: cl.exe, not gcc.
I'm curious what GCC would do if it wasn't purposely lobotomised and fed 300 GB of this nuclear waste.
They disabled optimisations:
> Lets compile the code, disabling optimizations with /Od to make sure that the pesky compiler doesn’t interfere with our algorithm