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.

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

Link to libgcc when statically linking musl #52091

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
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
9 changes: 9 additions & 0 deletions src/librustc_target/spec/linux_musl_base.rs
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,15 @@ pub fn opts() -> TargetOptions {
base.pre_link_objects_exe_crt.push("crti.o".to_string());
base.post_link_objects_crt.push("crtn.o".to_string());

// On some architectures (e.g. aarch64) musl depends on some libgcc
// functions (__addtf3, __multf3, __subtf3) for long double arithmetic that
// it uses internally. Unfortunately we don't provide these functions in
// compiler-builtins, so we instead need to get them from libgcc.
//
// This is not a problem if we are linking to libc dynamically since the
// libgcc dependency will automatically get picked up by the linker then.
base.post_link_objects_crt.push("-lgcc".to_string());

// These targets statically link libc by default
base.crt_static_default = true;
// These targets allow the user to choose between static and dynamic linking.
Expand Down