@@ -54,10 +54,10 @@ You can pretty much copy that output into your file. Start with a few modificati
54
54
` "panic-strategy": "abort" ` . If you decide not to ` abort ` on panicking, unless you [ tell Cargo
55
55
to] [ eh_personality ] , you must define an [ eh_personality] function.
56
56
- Configure atomics. Pick the first option that describes your target:
57
- - I have a single-core processor, no threads, ** no interrupts** , or any way for multiple things to
58
- be happening in parallel: if you are ** sure** that is the case, such as WASM (for now), you may
59
- set ` "singlethread": true ` . This will configure LLVM to convert all atomic operations to use
60
- their single threaded counterparts.
57
+ - I have a single-core processor, no threads, [ ** no interrupts** ] [ interrupts-note ] , or any way for
58
+ multiple things to be happening in parallel: if you are ** sure** that is the case, such as WASM
59
+ (for now), you may set ` "singlethread": true ` . This will configure LLVM to convert all atomic
60
+ operations to use their single threaded counterparts.
61
61
- I have native atomic operations: set ` max-atomic-width ` to the biggest type in bits that your
62
62
target can operate on atomically. For example, many ARM cores have 32-bit atomic operations. You
63
63
may set ` "max-atomic-width": 32 ` in that case.
@@ -108,6 +108,7 @@ You can pretty much copy that output into your file. Start with a few modificati
108
108
https://doc.rust-lang.org/edition-guide/rust-2018/error-handling-and-panics/aborting-on-panic.html
109
109
[ built-in-target ] : ./compiler-support.md#built-in-target
110
110
[ eh_personality ] : ./smallest-no-std.md#eh_personality
111
+ [ interrupts-note ] : https://github.com/rust-lang/rust/issues/58500#issuecomment-654341233
111
112
[ libcalls-atomic ] : http://llvm.org/docs/Atomics.html#libcalls-atomic
112
113
[ libcalls-sync ] : http://llvm.org/docs/Atomics.html#libcalls-sync
113
114
[ gcc-sync ] : https://gcc.gnu.org/onlinedocs/gcc/_005f_005fsync-Builtins.html
0 commit comments