Fix naming for redbean shared memory atomics

This commit is contained in:
Justine Tunney 2022-10-06 09:41:22 -07:00
parent a5b483f2d4
commit 60b68d7152
No known key found for this signature in database
GPG key ID: BE714B4575D6E328
4 changed files with 18 additions and 12 deletions

View file

@ -4620,7 +4620,7 @@ UNIX MODULE
This operation happens atomically and provides the same memory
barrier semantics as the aligned x86 LOCK CMPXCHG instruction.
unix.Memory:add(word_index:int, value:int)
unix.Memory:fetch_add(word_index:int, value:int)
└─→ old:int
Fetches then adds value.
@ -4632,7 +4632,7 @@ UNIX MODULE
This operation is atomic and provides the same memory barrier
semantics as the aligned x86 LOCK XADD instruction.
unix.Memory:and(word_index:int, value:int)
unix.Memory:fetch_and(word_index:int, value:int)
└─→ int
Fetches and bitwise ands value.
@ -4640,7 +4640,7 @@ UNIX MODULE
This operation happens atomically and provides the same memory
barrier ordering semantics as its x86 implementation.
unix.Memory:or(word_index:int, value:int)
unix.Memory:fetch_or(word_index:int, value:int)
└─→ int
Fetches and bitwise ors value.
@ -4648,7 +4648,7 @@ UNIX MODULE
This operation happens atomically and provides the same memory
barrier ordering semantics as its x86 implementation.
unix.Memory:xor(word_index:int, value:int)
unix.Memory:fetch_xor(word_index:int, value:int)
└─→ int
Fetches and bitwise xors value.