Fix Atomic issue on Cranelift compiler not related to Notify/Wait opcodes #3162
Labels
Milestone
Comments
ptitSeb
added a commit
that referenced
this issue
Sep 6, 2022
ptitSeb
added a commit
that referenced
this issue
Nov 22, 2022
bors bot
added a commit
that referenced
this issue
Nov 29, 2022
3153: SharedMemory & Atomics r=ptitSeb a=ptitSeb # Description Enabled SharedMemory and the Atomics extension proposal - [x] Enable Atomic extension by default - [x] Fix "imports" tests #3154 - [x] Add function for memory.atomic.wait32, memory.atomic.wait64 and memory.atomic.notify opcodes #3155 - [x] Add support for the new wait/notify opcodes in Cranelift compiler #3156 - [x] Add support for the new wait/notify opcodes in LLVM compiler #3157 - [x] Add support for atomic access opcodes in AArch64/Singlepass compiler #3159 - [x] Add support for the new wait/notify opcodes in Singlepass compiler #3158 - [x] Fix Atomic issues on x86_64 Singlepass compiler not related to Wait/Notify opcodes #3161 - [x] Fix Atomic issues on Cranelift compiler not related to Wait/Notify opcodes #3162 - [x] Fix Atomic issues on LLVM compiler not related to Wait/Notify opcodes #3163 - [x] Fix the ticket #3167 on Cranelift For #3304 Co-authored-by: John Sharratt's Shared Account <johnathan.sharratt@gmail.com> Co-authored-by: ptitSeb <sebastien.chev@gmail.com> Co-authored-by: Syrus Akbary <me@syrusakbary.com>
|
Merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
On feat_sharedmemory branch, enabling the threads::atomics test on the Cranelift compiler fail on multiple place, not related to the missing Wait/Notify opcodes. Most of the fails are
wich seems to be a error label issue.
The text was updated successfully, but these errors were encountered: