feat(icicle): Add icicle MSM support

[sagar-a16z]

• Rebased feat(icicle): Add icicle msm support #322
• Updated to latest icicle release
• Fixed it to use the GPU correctly
• Fall back to JOLT's CPU implementations when GPU is unavailable - much faster than the default CPU impl.
• Added msm benchmarks
• Overall Perf is up ~20%.

[wiz-a16z]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities
Sensitive Data
Secrets
IaC Misconfigurations
Total

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[sagar-a16z]

With the newest benchmark I added, the GPU perf is actually really good. (This is a WSL machine on a 5800X3D + 3080TI)

CPU

VariableBaseMSM::msm() [mode:JOLT CPU]
                        time:   [807.29 ms 810.86 ms 814.58 ms]

GPU

VariableBaseMSM::msm() [mode:Icicle]
                        time:   [153.71 ms 156.67 ms 159.43 ms]

It’s WAY faster. For some reason it's much slower when running the examples. Maybe because my CPU usage was low while this benchmark ran where as the CPU is pinned when running the examples or maybe because I have plenty of left over memory.

[moodlezoup]

great work! main question is: I think we need to move the icicle init into prove; otherwise if someone is e.g. loading the preprocessing from disk and running prove by itself, icicle won't be initialized. wdyt?

[moodlezoup]

Should this be moved to prove?

[sagar-a16z]

I had moved this to preprocessing to keep off the critical path in my tests but you're right, it needs to be inside of prove but it can also remain inside of preprocessing. Calling it multiple times does nothing so should be safe to do.