I just isolated a truly bizarre performance bug - 64-bit size_t is 1.5x as fast as uint32_t in my simulation code. It's either a compiler codegen problem, CPU OoO/pipeline problem, or an integer overflow somewhere. :woozy_baa:
size_t
uint32_t
@niconiconi any divisions present? If not it's really bizarre, because casting down to u32 could be pushed off to the very end.
QOTO: Question Others to Teach Ourselves An inclusive, Academic Freedom, instance All cultures welcome. Hate speech and harassment strictly forbidden.