Skip to content

Speccpu limitations on Windows & specifying benchmarks in SPECCpuExecutor #619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
saibulusu merged 3 commits into from
Jan 17, 2026
Merged

Speccpu limitations on Windows & specifying benchmarks in SPECCpuExecutor #619

saibulusu merged 3 commits into from
Jan 17, 2026
+84 −25

Conversation

@saibulusu
Copy link
Member

@saibulusu saibulusu commented Jan 17, 2026 •
edited
Loading

  • When running on Windows, we are not able to run every benchmark for speccpu via VC (as of right now). This is called out clearly in our profiles now.
  • The capacity to specify benchmarks and/or suites (as opposed to only 1 suite) has been added for the SPECCpuExecutor as well.
  • Using 'gcc-core' in place of 'gcc' from cygwin as the package name has changed. 'gcc-core' still produces a gcc executable.

@saibulusu saibulusu enabled auto-merge (squash) January 17, 2026 00:55
@saibulusu saibulusu merged commit e334791 into main Jan 17, 2026
5 checks passed
@saibulusu saibulusu deleted the users/saibulusu/speccpu-changes branch January 17, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@brdeyo brdeyo brdeyo approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@saibulusu @brdeyo