"The reason is that the compiler decided to allocate the backing store on the stack. Because it knows what size it needs to be (10 times the size of a task) it can allocate storage for it in the stack frame of process2 instead of on the heap1. Note that this depends on the fact that the backing store does not escape to the heap inside of processAll."
This is definitionally small-object boxing optimizations.
Originally read "BOM (Bill of Materials)" and thought it was a misattribution of the more common "Byte Order Marker" acronym common to file format headers, but websurfing reveals it's correct -- referring to this format's origin in Installers, haha.
> The bill of materials file appeared in NeXTSTEP to support installation. The file format was updated and extended for Mac OS X 10.0. The format was extended to support 64 bit file sizes with OS X 10.3.
Is the feedback that instead of a short web search, I could "simply" have checked the man page on a different computer, after confirming dev tools are installed?
Thinking about fpu pipeline parallelism/stalls still matter, though more often by hinting an optimizing compiler + verifying the output by inspection, than by inlining asm itself.
reply