Repository navigation
refactor(bazel): drop the generated Linux toolchain wrapper scripts #3832
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
Closed
Alexandr-Solovev
wants to merge
6
commits into
uxlfoundation:main
from
Alexandr-Solovev:dev/asolovev_bazel_drop_lnx_wrappers
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8ffcb3a
refactor(bazel): remove dead code and fix the template file name typo
Alexandr-Solovev e103b1b
refactor(bazel): share the platform-independent toolchain config
Alexandr-Solovev ef5acc7
refactor(bazel): patch the kernel defines with a stock Bazel action
Alexandr-Solovev 30f1fbd
refactor(bazel): drop the generated Linux toolchain wrapper scripts
3497aba
docs(bazel): scope the merge docstring to what each platform passes
Alexandr-Solovev e8293ca
review: drop the empty file attributes from the Linux cc_toolchain
Alexandr-Solovev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coverage note: on x86 with MKL this branch never runs.
aquery 'mnemonic("MergeStaticLibraries", ...)'finds 0 actions for host//:release, DPC//:release, and//cpp/... + //examples/.... It only fires when a prebuilt.ais in the linking context, i.e.--backend_config=ref(libonedal_thread.a<-libonedal_thread_no_deps.a+libopenblas.a).I built static OpenBLAS 0.3.34 with
.ci/env/openblas.shand ran that config: the MRI script works with the bzlmod+paths and the release tree is byte-identical to base. So the aarch64/rv64 OpenBLAS jobs are the only CI coverage of this code - worth stating in the description.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed independently, and agreed it belongs in the description.
Reproduced the 0-action result here on x86 with MKL:
And pinned down exactly where the flag that does reach it lives —
--backend_config=refappears in two places in CI and nowhere else:.github/workflows/ci-aarch64.ymllines 253, 305, 330 — theLinuxBazel_OpenBLAS(SVE)jobs.ci/pipeline/ci.ymlline 717 —CI (LinuxBazelGNU_OpenBLAS_rv64)So your conclusion holds: the aarch64 and rv64 OpenBLAS jobs are the only CI coverage of the MRI branch. The x86 jobs exercise the Windows
libbranch and the unchanged link paths instead. I could not re-run therefconfig locally — this worktree has no static OpenBLAS, andaquery --backend_config=refstops atCannot locate +openblas_repo+openblas dependency— so I am taking your byte-identicalrefrelease tree on report rather than claiming it myself.Your docstring point is also right, and it was wrong in both the summary line and the
Args:entry. Only lines 121 and 252 passall_object_list, and both sit insideif is_windows; the Linux-reachable call sites at 150, 198 and 207 passunpacked_linking_context.static_librariesalone. Fixed in 3497aba://:releasestill analyses clean after it. Docstring-only, so no action re-execution.The coverage paragraph above is not in the description yet — I will get it in there.