Open daniestevez opened 7 months ago
I noticed this error. It looks like a weird issue between the Rust compiler and LLVM. Perhaps it does not propagate the extension flags correctly?
In any case, it produces a working binary, so it is not critical (it is annoying, though)
I forgot to mention that this didn't happen with an earlier version of riscv-rt
(or maybe it was with an earlier version of rustc
; I forgot of what I updated when this started happening). I agree that the problem is not at all critical.
The previous version of riscv-rt
used pre-compiled blobs linked at compile time. Now, we use inline assembly, and the Rust compiler includes the assembly code in the build process. I'll ask the rest of the Rust Embedded working group about this issue, they can suggest where to open an issue.
This is a known issue. https://github.com/rust-lang/rust/issues/80608
I found this problem first in https://github.com/daniestevez/galileo-osnma/issues/23, but the following self-contained example replicates the problem: https://github.com/daniestevez/riscv/tree/debug-mul-build/riscv-rt/test-build
When this example is built with
cargo build --release
, I get the following:Despite the error, an executable is produced.
If I build without
--release
instead, I get: