Skip to content

Verify the current resolution #490

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

Merged
merged 16 commits into from
May 10, 2025

Conversation

helly25
Copy link
Contributor

@helly25 helly25 commented Apr 27, 2025

  • Split llvm_release_name into two:
    • llvm_release_name_host_info: Used to verify the resolution. It does not take a rctx.
    • llvm_release_name_context: Will fail if resolution from rctx fails.
  • Change dist_version_arch to host_info which returns a struct, so the result can easily be extended and only one call is needed.

As can be seen in toolchain/internal/llvm_distributions.golden.sel.txt there are a number of decisions taken in mode auto that lead to failures in predicting a correct LLVM distribution. Those we should fix.

helly25 added a commit to helly25/bazel-toolchain that referenced this pull request Apr 28, 2025
helly25 added 12 commits May 2, 2025 16:19
* Split `llvm_release_name` into two:
  * `llvm_release_name_host_info`: Used to verify the resolution. It does not take a rctx.
  * `llvm_release_name_context`: Will fail if resolution from rctx fails.
* Change `dist_version_arch` to `host_info` which returns a struct, so the result can easily be extended and only one call is needed.
Show a selection as ERROR if the selected arch differs from the specified arch.
@helly25 helly25 force-pushed the feat/verify_resolution_20250427 branch from 06987ab to 5830340 Compare May 2, 2025 16:21
@helly25
Copy link
Contributor Author

helly25 commented May 3, 2025

@fmeum Any chance you can review and we can progress on this? I want to use this as a basis and verification of improvements to finding targets automatically.

@helly25 helly25 requested a review from fmeum May 3, 2025 12:47
@helly25
Copy link
Contributor Author

helly25 commented May 7, 2025

@fmeum any other comments/questions/concerns?

@fmeum fmeum merged commit 60c9695 into bazel-contrib:master May 10, 2025
36 checks passed
@helly25 helly25 deleted the feat/verify_resolution_20250427 branch May 10, 2025 12:39
helly25 added a commit to helly25/bazel-toolchain that referenced this pull request May 10, 2025
helly25 added a commit to helly25/bazel-toolchain that referenced this pull request May 10, 2025
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