Skip to content

[UBTI] Always use LLD on Linux #10783

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

Merged
teqdruid merged 1 commit into from
Jul 7, 2026
+4 −2
Merged

[UBTI] Always use LLD on Linux #10783

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .github/workflows/unifiedBuildTestAndInstall.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,6 +208,8 @@ jobs:
# Setup z3 for Linux and macOS. This hasn't been working on Windows through
# `choco install z3`, so don't turn on z3 for those runs.
#
# 'ld' is known to perform poorly on MLIR, so always use lld on Linux.
#
# Any runner-specific CMAKE configuration can be put into the `cmake` output.
# These will be used when running `cmake` later.
- name: Setup (linux)
Expand All @@ -222,8 +224,8 @@ jobs:
fi

sudo apt-get update
sudo apt-get install "$COMPILER" iverilog libsystemc-dev ninja-build valgrind z3
echo cmake="-DLLVM_ENABLE_Z3_SOLVER=ON" >> "$GITHUB_OUTPUT"
sudo apt-get install "$COMPILER" iverilog libsystemc-dev ninja-build valgrind z3 lld
echo cmake="-DLLVM_ENABLE_Z3_SOLVER=ON -DLLVM_ENABLE_LLD=ON" >> "$GITHUB_OUTPUT"
- name: Restore Verilator Cache (Linux)
if: inputs.run_integration_tests && runner.os == 'Linux'
id: cache-verilator
Expand Down