More arithmetic benchmarks

[gatesn]

No description provided.

[codspeed-hq]

Merging this PR will degrade performance by 19.47%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚡ 6 improved benchmarks
❌ 105 regressed benchmarks
✅ 1426 untouched benchmarks
🆕 8 new benchmarks
⏩ 10 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	compare[48]	213 µs	300.6 µs	-29.15%
❌	Simulation	compare[50]	227.7 µs	319.1 µs	-28.64%
❌	Simulation	compare[49]	228.2 µs	317.7 µs	-28.18%
❌	Simulation	compare[44]	207.5 µs	287.7 µs	-27.87%
❌	Simulation	compare[46]	218.5 µs	302.5 µs	-27.75%
❌	Simulation	compare[47]	223.5 µs	309.3 µs	-27.74%
❌	Simulation	compare[40]	190.7 µs	263.4 µs	-27.62%
❌	Simulation	compare[44]	212.2 µs	292.3 µs	-27.43%
❌	Simulation	compare[45]	218.9 µs	300.9 µs	-27.26%
❌	Simulation	compare[43]	209.2 µs	287.6 µs	-27.26%
❌	Simulation	compare[42]	204.6 µs	281 µs	-27.2%
❌	Simulation	compare[40]	195.6 µs	268.3 µs	-27.1%
❌	Simulation	compare[43]	214.2 µs	292.5 µs	-26.77%
❌	Simulation	compare[42]	209.4 µs	285.9 µs	-26.75%
❌	Simulation	compare[41]	204.5 µs	279.2 µs	-26.74%
❌	Simulation	compare[41]	209.3 µs	284 µs	-26.27%
❌	Simulation	compare[39]	199.9 µs	270.8 µs	-26.18%
❌	Simulation	compare[31]	157.7 µs	213.7 µs	-26.18%
❌	Simulation	compare[38]	195.5 µs	264.6 µs	-26.09%
❌	Simulation	compare[36]	187.3 µs	252.6 µs	-25.85%
...	...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing ngates/arith-bench (8b3ccf2) with develop (d0013ff)}

Footnotes

1. 10 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩