From 65614e91ad847e3d2941e1308bb2b1d916eba25f Mon Sep 17 00:00:00 2001 From: Scott Mabin Date: Tue, 22 Feb 2022 10:44:56 +0000 Subject: [PATCH] riscv32imc_esp_espidf: set max_atomic_width to 64 --- compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs b/compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs index fb084afe960..d506e7f6aac 100644 --- a/compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs +++ b/compiler/rustc_target/src/spec/riscv32imc_esp_espidf.rs @@ -18,11 +18,11 @@ pub fn target() -> Target { cpu: "generic-rv32".to_string(), // 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(32)` + // the __atomic* and __sync* GCC builtins, so setting `max_atomic_width` to `Some(64)` // 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. - max_atomic_width: Some(32), + max_atomic_width: Some(64), atomic_cas: true, features: "+m,+c".to_string(),