Skip to content
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.

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

cycleclock: Use clock_gettime() as fallback for any Linux architecture #1899

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

hdeller
Copy link
Contributor

@hdeller hdeller commented Jan 8, 2025

The Linux kernel provides the clock_gettime() functions since a long time already, so it's possible to use it as a generic fallback option for any architecture if no other (better) possibility has been provided instead.

I noticed the benchmark package failed to build on debian on the SH-4 architecture, so with this change SH-4 is now the first user of this fallback option.

The Linux kernel provides the clock_gettime() functions since a long
time already, so it's possible to use it as a generic fallback option
for any architecture if no other (better) possibility has been provided
instead.

I noticed the benchmark package failed to build on debian on the SH-4
architecture, so with this change SH-4 is now the first user of this
fallback option.
@hdeller
Copy link
Contributor Author

hdeller commented Jan 8, 2025

As can be seen here:
https://buildd.debian.org/status/package.php?p=benchmark&suite=sid
sh-4 was the last architecture on which building this package failed.

@dmah42 dmah42 changed the title cycleclock: Use cock_gettime() as fallback for any Linux architecture cycleclock: Use clock_gettime() as fallback for any Linux architecture Jan 8, 2025
@dmah42 dmah42 merged commit 077db43 into google:main Jan 8, 2025
75 of 86 checks passed
@hdeller hdeller deleted the sh4-cycleclock branch January 8, 2025 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants