blockifier: add benchmarking and only-native feature flags

[avi-starkware]

Adds two new feature flags:

• `benchmarking`: gates time/call_counter fields on CallInfo and
  EntryPointExecutionContext for execution profiling
• `only-native`: forces native execution path even when tracked
  resource is CairoSteps

Zero behavior change without flags enabled.

---

Note

Medium Risk
Low impact by default, but when enabled this changes execution-path selection (forcing native execution) and adds new data fields to CallInfo, which could affect consumers expecting a stable struct layout/serialization behind feature gates.

Overview
Adds two new opt-in feature flags to blockifier: benchmarking and only-native.

With benchmarking enabled, execution populates per-call profiling metadata (time and call_counter) on CallInfo, backed by a counter in EntryPointExecutionContext. With only-native enabled (and cairo_native), the dispatcher no longer falls back to the VM path for TrackedResource::CairoSteps, forcing the native executor.

Updates tests/fixtures to construct CallInfo via ..Default::default() so new optional fields don’t break compilation, and derives serde for CallSummary/ExecutionSummary when transaction_serde is enabled.

^{Reviewed by Cursor Bugbot for commit 4d74bec. Bugbot is set up for automated code reviews on this repo. Configure here.}

[reviewable-StarkWare]

This change is 

[avi-starkware]

• blockifier: add sierra-emu execution behind feature flag #13543
• blockifier: introduce ContractExecutor abstaction #13542
• blockifier: add with-libfunc-profiling feature flag #13755
• blockifier: add benchmarking and only-native feature flags #13541 👈 (View in Graphite)
• main-v0.14.2

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

[github-actions]

Artifacts upload workflows:

• Started at 2026-03-26T17:21:52Z
• Started at 2026-03-26T17:23:25Z
• Started at 2026-03-26T17:21:52Z
• Started at 2026-03-26T17:37:31Z
• Started at 2026-03-26T17:38:05Z
• Started at 2026-03-26T19:16:16Z
• Started at 2026-03-26T19:16:37Z
• Started at 2026-04-06T16:31:39Z
• Started at 2026-04-06T16:39:07Z
• Started at 2026-04-06T20:33:02Z
• Started at 2026-04-06T20:33:02Z
• Started at 2026-04-08T05:04:59Z
• Started at 2026-04-08T05:05:15Z
• Started at 2026-04-14T10:59:42Z
• Started at 2026-04-14T12:42:45Z
• Started at 2026-04-19T09:29:16Z

[TomerStarkware]

@TomerStarkware reviewed 9 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on noaov1 and Yoni-Starkware).

[Yoni-Starkware]

@Yoni-Starkware reviewed 2 files and all commit messages, and made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on avi-starkware, noaov1, and TomerStarkware).

---

crates/blockifier/src/execution/entry_point_execution.rs line 526 at r2 (raw file):

        time: Default::default(),
        #[cfg(feature = "benchmarking")]
        call_counter: 0,

@TomerStarkware why do we need this? can't you just count the number of nested calls at the end of the run?

Code quote:

        #[cfg(feature = "benchmarking")]
        call_counter: 0,

[cursor]

PR Summary

Medium Risk
Adds new optional execution behavior and data collection paths: enabling only-native can change which engine executes calls, and benchmarking changes CallInfo shape and how results are produced under that flag.

Overview
Adds two new blockifier feature flags: benchmarking and only-native.

With benchmarking, CallInfo now includes a gated time: Duration field and execute_entry_point_call measures wall-clock duration for each entry-point execution (Cairo0, Cairo1, and native) and records it on the returned CallInfo.

With only-native, when cairo_native is enabled the executor will always take the native path for RunnableCompiledClass::V1Native even when the tracked resource is CairoSteps (previously it fell back to the VM path). Related test fixtures were updated to use ..Default::default() for the new optional field(s), and CallSummary/ExecutionSummary now derive serde when transaction_serde is enabled.

^{Reviewed by Cursor Bugbot for commit bfe0a84. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Yoni-Starkware]

@Yoni-Starkware reviewed 7 files and all commit messages, made 1 comment, and resolved 1 discussion.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on avi-starkware and noaov1).

---

crates/blockifier/src/execution/entry_point.rs line 331 at r3 (raw file):

    // Used to support charging for gas consumed in blockifier revert flow.
    pub sierra_gas_revert_tracker: SierraGasRevertTracker,

Revert the newline