feat: add corelib benchmarks and refactor to shared bench_all_phases helper

[orizi]

TL;DR

Added a new benchmark that measures compilation performance of the corelib itself, alongside the existing fib.cairo benchmark.

What changed?

The benchmark infrastructure was refactored to extract reusable build_db and build_test_db helper functions, eliminating repeated RootDatabase builder boilerplate. The benchmark phases (cairo-to-sierra, cairo-to-diagnostics, cairo-to-testing, cairo-to-cache, cache-to-sierra, cache-to-testing) were extracted into a generic bench_all_phases function that accepts a path, group name, label, and a detect_core flag.

A new bench_compile_corelib benchmark was added that runs all the same phases against the corelib directory (with detect_core: false), and both bench_compile and bench_compile_corelib are now registered with criterion_group!.

How to test?

Run the benchmarks with:

cargo bench --bench compile

Both the compile and compile_corelib benchmark groups should appear in the output.

Why make this change?

Benchmarking only a small example file like fib.cairo does not capture the performance characteristics of compiling a large, real-world codebase. Adding corelib as a benchmark target provides a more representative and meaningful measure of compiler performance at scale.

[orizi]

• feat: add corelib benchmarks and refactor to shared bench_all_phases helper #9859 👈 (View in Graphite)
• feat: add cache-to-testing compile benchmark #9858
• feat: add cairo-to-cache and cache-to-sierra compile benchmarks #9857
• feat: add cairo-to-testing benchmark #9856
• feat: add diagnostics phase benchmark #9855
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[reviewable-StarkWare]

This change is 

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 45feb8b392

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[eytan-starkware]

@eytan-starkware reviewed 2 files and all commit messages, and made 2 comments.
Reviewable status: 2 of 3 files reviewed, 2 unresolved discussions (waiting on orizi and TomerStarkware).

---

tests/benches/compile.rs line 52 at r2 (raw file):

    // Phase: source → Sierra (full IR generation).
    group.bench_function("cairo-to-sierra", |b| {

Dont we need separate function names for differrent benchmarks?

---

tests/benches/compile.rs line 189 at r2 (raw file):

}

criterion_group!(benches, bench_compile);

Wont this give

[orizi]

@orizi made 2 comments.
Reviewable status: 2 of 3 files reviewed, 2 unresolved discussions (waiting on eytan-starkware and TomerStarkware).

---

tests/benches/compile.rs line 52 at r2 (raw file):

Previously, eytan-starkware wrote…

Dont we need separate function names for differrent benchmarks?

the groups seems to be enough.

---

tests/benches/compile.rs line 189 at r2 (raw file):

Previously, eytan-starkware wrote…

Wont this give

?

[eytan-starkware]

@eytan-starkware made 1 comment and resolved 1 discussion.
Reviewable status: 2 of 3 files reviewed, 1 unresolved discussion (waiting on orizi and TomerStarkware).

---

tests/benches/compile.rs line 52 at r2 (raw file):

Previously, orizi wrote…

the groups seems to be enough.

I am thinking it will be better to see for each phase how each benchmark behaved, currently it will be hard to compare a slowdown in phase x, as we will need to compare 3 different tables

[orizi]

@orizi made 1 comment.
Reviewable status: 0 of 3 files reviewed, 1 unresolved discussion (waiting on eytan-starkware and TomerStarkware).

---

tests/benches/compile.rs line 52 at r2 (raw file):

Previously, eytan-starkware wrote…

I am thinking it will be better to see for each phase how each benchmark behaved, currently it will be hard to compare a slowdown in phase x, as we will need to compare 3 different tables

i flipped it now.

[eytan-starkware]

@eytan-starkware reviewed 3 files and all commit messages, made 1 comment, and resolved 1 discussion.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on TomerStarkware).