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.

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

Jump to bottom

rfe: clang doesn't select the linker suitable for target #121355

Open
stsp opened this issue Dec 30, 2024 · 1 comment
Open

rfe: clang doesn't select the linker suitable for target #121355

stsp opened this issue Dec 30, 2024 · 1 comment
Labels
clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl'

Comments

@stsp
Copy link

stsp commented Dec 30, 2024

When clang is passed, say,
-target aarch64-unknown-linux-gnu -fuse-ld=bfd
it doesn't invoke aarch64-unknown-linux-gnu-ld
but just ld.bfd.
I wonder if it is intentional, or just a not implemented
feature?
@github-actions github-actions bot added the clang Clang issues not falling into any other category label Dec 30, 2024
@EugeneZelenko EugeneZelenko added clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl' and removed clang Clang issues not falling into any other category labels Dec 30, 2024
@llvmbot
Copy link
Member

llvmbot commented Dec 30, 2024

@llvm/issue-subscribers-clang-driver

Author: Stas Sergeev (stsp)

When clang is passed, say, `-target aarch64-unknown-linux-gnu -fuse-ld=bfd` it doesn't invoke `aarch64-unknown-linux-gnu-ld` but just `ld.bfd`. I wonder if it is intentional, or just a not implemented feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clang:driver 'clang' and 'clang++' user-facing binaries. Not 'clang-cl'
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@stsp @EugeneZelenko @llvmbot