Yusuf Abdulghani (Local) <yaghani@mac.com> writes: > > I figured out that the stack was the culprit. For what it's worth, speed.c deliberately uses the stack to avoid address clashes on cpus with direct mapped caches. Perhaps it should forget about that above a certain size, or have an option to that effect at least.