mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Set max_atomic_width for riscv32*-esp-espidf to 32

Browse Source
This commit is contained in:
Taiki Endo 2023-09-23 20:44:03 +09:00
parent 3050938abd
commit ecefd4eb3f
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
compiler/rustc_target/src/spec/riscv32imac_esp_espidf.rs
View File

@ -17,7 +17,7 @@ pub fn target() -> Target {
// As RiscV32IMAC architecture does natively support atomics, // As RiscV32IMAC architecture does natively support atomics,
// automatically enable the support for the Rust STD library. // automatically enable the support for the Rust STD library.
max_atomic_width: Some(64), max_atomic_width: Some(32),
atomic_cas: true, atomic_cas: true,
features: "+m,+a,+c".into(), features: "+m,+a,+c".into(),

4
compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs
View File

@ -16,11 +16,11 @@ pub fn target() -> Target {
cpu: "generic-rv32".into(), cpu: "generic-rv32".into(),
// While the RiscV32IMC architecture does not natively support atomics, ESP-IDF does support // While the RiscV32IMC architecture does not natively support atomics, ESP-IDF does support
// the __atomic* and __sync* GCC builtins, so setting `max_atomic_width` to `Some(64)` // the __atomic* and __sync* GCC builtins, so setting `max_atomic_width` to `Some(32)`
// and `atomic_cas` to `true` will cause the compiler to emit libcalls to these builtins. // and `atomic_cas` to `true` will cause the compiler to emit libcalls to these builtins.
// //
// Support for atomics is necessary for the Rust STD library, which is supported by the ESP-IDF framework. // Support for atomics is necessary for the Rust STD library, which is supported by the ESP-IDF framework.
max_atomic_width: Some(64), max_atomic_width: Some(32),
atomic_cas: true, atomic_cas: true,
features: "+m,+c".into(), features: "+m,+c".into(),