diff options
| author | Julian Frimmel <julian@fri-me.de> | 2024-10-15 23:07:00 +0200 |
|---|---|---|
| committer | Julian Frimmel <julian@fri-me.de> | 2024-10-17 09:00:08 +0200 |
| commit | a35ed2f9eb52176b14e27f0f39229015cf035a30 (patch) | |
| tree | 6c83868444796c5c2eb9b8ab76fa9d084f0eb267 /compiler/rustc_codegen_llvm/src | |
| parent | bb8db13892ced757faf1c0206c70f313cd4b23c0 (diff) | |
| download | rust-a35ed2f9eb52176b14e27f0f39229015cf035a30.tar.gz rust-a35ed2f9eb52176b14e27f0f39229015cf035a30.zip | |
Use `rust-lld` instead of `avr-gcc` as the linker
This fixes the [build error] caused by the `avr-gcc` (used as linker) not being available in the Rust CI. This is a viable solution, which shows the wrong/right behavior and, since no functions from `libgcc` are called, does not produce errors. This was discussed [here]. Another small problem is, that `lld` doesn't link the correct startup-code by default. This is not a problem for this test (since it does not actually use anything the startup code is needed for (no variables, no stack, no interrupts)), but this causes the `main`-function to be removed by the default flag `--gc-sections`. Therefore the `rmake`-driver also adds the linker flag `--entry=main` to mark the `main`-function as the entry point and thus preventing it from getting removed. The code would work on a real AVR device. [build error]: https://github.com/rust-lang/rust/pull/131755#issuecomment-2415127952 [here]: https://github.com/rust-lang/rust/pull/131755#issuecomment-2416469675
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions