Skip to content

Conversation

@IceTDrinker
Copy link
Member

  • this would not give an average runtime for scalar benchmarks and for small precisions could give super good timings (for lucky values)
  • the timings for other precisions could still be favorable or unfavorable depending on the value that was drawn

- this would not give an average runtime for scalar benchmarks and for
small precisions could give super good timings (for lucky values)
- the timings for other precisions could still be favorable or unfavorable
depending on the value that was drawn
@IceTDrinker
Copy link
Member Author

might have missed some cases

@IceTDrinker IceTDrinker marked this pull request as ready for review November 24, 2025 15:48
Copy link
Contributor

@tmontaigu tmontaigu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tmontaigu reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @soonum)

@IceTDrinker IceTDrinker merged commit caf5e9d into main Nov 25, 2025
248 of 249 checks passed
@IceTDrinker IceTDrinker deleted the am/chore/bench-scalar branch November 25, 2025 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants