undefined | Better HN

0 pointsdahfizz3y ago0 comments

> autovectorizing is broken by bounds checks

This is the big one. You pay a 50% penalty for actual CPU bound, iteration heavy code with bounds checking enabled.

0 comments

The proper way of addressing that is to manually hoist bound checks out of "hot" loops. Not just remove them altogether.

This should be the article.

Running this with 1.65 on an Intel 12400 gets a nearly 4x speedup when bounds checking is not needed. Just wow.

Bounds checking avoidance is important when it becomes a significant chunk of your hot-path.

j / k navigate · click thread line to collapse

0 pointsdahfizz3y ago0 comments

> autovectorizing is broken by bounds checks

This is the big one. You pay a 50% penalty for actual CPU bound, iteration heavy code with bounds checking enabled.

The proper way of addressing that is to manually hoist bound checks out of "hot" loops. Not just remove them altogether.

This should be the article.

Running this with 1.65 on an Intel 12400 gets a nearly 4x speedup when bounds checking is not needed. Just wow.

Bounds checking avoidance is important when it becomes a significant chunk of your hot-path.

j / k navigate · click thread line to collapse