[libc] Fix issue with using clock() in hermetic testing #146069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #145349. Some targets (like baremetal) don't implement
clock()
. However, they may later be overridden (e.g. by semihosting libraries), therefore, we make it[[gnu::weak]]
. This resolves one of the errors when building hermetic tests downstream.I plan to use the embedding API to implement
clock()
later, however, that is out of scope of this PR. Also, this allows for other architectures to start testing without aclock()
implementation.