You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2024. It is now read-only.
Just wanted to give some feedback. I'm evaluating sold for rustc/bazel/rules_rust, but I cannot find a working way to use it.
If I specify -C linker=ld64.mold (via --@rules_rust//:extra_rustc_flag=), then rustc generates linker argument -m64 which mold does not understand.
If I specify -C linker=mold, then rustc additionally generates -arch x86_64 which mold does not understand.
I played around with various values of -C linker-flavor, but none seem to generate better args for mold. In particular, the lld flavors don't work because rustc will specify -flavor.
By default, rustc adds -dead_strip or -Wl,-dead_strip, which would be nice to retain.
Rustc when invoked with cargo seems to work fine somehow. I don't know if the differences are in Bazel or in our project configuration, which is quite elaborate because we're cross-compiling for ios.
Cheers, Bram
The text was updated successfully, but these errors were encountered:
Hi,
Just wanted to give some feedback. I'm evaluating sold for rustc/bazel/rules_rust, but I cannot find a working way to use it.
-C linker=ld64.mold
(via--@rules_rust//:extra_rustc_flag=
), thenrustc
generates linker argument-m64
which mold does not understand.-C linker=mold
, thenrustc
additionally generates-arch x86_64
which mold does not understand.-C linker-flavor
, but none seem to generate better args for mold. In particular, the lld flavors don't work because rustc will specify-flavor
.-dead_strip
or-Wl,-dead_strip
, which would be nice to retain.Rustc when invoked with cargo seems to work fine somehow. I don't know if the differences are in Bazel or in our project configuration, which is quite elaborate because we're cross-compiling for ios.
Cheers, Bram
The text was updated successfully, but these errors were encountered: