From c023edd9853a810b8c54b0605134c23995e7472c Mon Sep 17 00:00:00 2001 From: Steven Walter Date: Mon, 11 May 2020 19:44:42 -0400 Subject: [PATCH] rust.inc: make max-atomic-width an integer As a string this was actually being ignored. It mostly didn't matter because max-atomic-width falls back to target-pointer-size, and they are usually the same. However, at least on i586, 64-bit atomics are supported with a 32-bit pointer size. --- recipes-devtools/rust/rust.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-devtools/rust/rust.inc b/recipes-devtools/rust/rust.inc index 7c01f29..cdcc983 100644 --- a/recipes-devtools/rust/rust.inc +++ b/recipes-devtools/rust/rust.inc @@ -313,7 +313,7 @@ def rust_gen_target(d, thing, wd, features, cpu): tspec = {} tspec['llvm-target'] = d.getVarFlag('LLVM_TARGET', arch) tspec['data-layout'] = d.getVarFlag('DATA_LAYOUT', arch) - tspec['max-atomic-width'] = d.getVarFlag('MAX_ATOMIC_WIDTH', arch) + tspec['max-atomic-width'] = int(d.getVarFlag('MAX_ATOMIC_WIDTH', arch)) tspec['target-pointer-width'] = d.getVarFlag('TARGET_POINTER_WIDTH', arch) tspec['target-c-int-width'] = d.getVarFlag('TARGET_C_INT_WIDTH', arch) tspec['target-endian'] = d.getVarFlag('TARGET_ENDIAN', arch)