Atomics.and()
The static Atomics.and()
method computes a bitwise AND with a given value at a given position in the array, and returns the old value at that position. This atomic operation guarantees that no other write happens until the modified value is written back.
Syntax
Atomics.and(typedArray, index, value)
Parameters
typedArray
-
An integer typed array. One of
Int8Array
,Uint8Array
,Int16Array
,Uint16Array
,Int32Array
,Uint32Array
,BigInt64Array
, orBigUint64Array
. index
-
The position in the
typedArray
to compute the bitwise AND. value
-
The number to compute the bitwise AND with.
Return value
The old value at the given position (typedArray[index]
).
Exceptions
- Throws a
TypeError
, iftypedArray
is not one of the allowed integer types. - Throws a
RangeError
, ifindex
is out of bounds in thetypedArray
.
Description
The bitwise AND operation only yields 1, if both a
and b
are 1. The truth table for the AND operation is:
a | b | a & b |
---|---|---|
0 | 0 | 0 |
0 | 1 | 0 |
1 | 0 | 0 |
1 | 1 | 1 |
For example, a bitwise AND of 5 & 1
results in 0001
which is 1 in decimal.
5 0101 1 0001 ---- 1 0001
Examples
Using and()
const sab = new SharedArrayBuffer(1024); const ta = new Uint8Array(sab); ta[0] = 5; Atomics.and(ta, 0, 1); // returns 0, the old value Atomics.load(ta, 0); // 1
Specifications
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | WebView Android | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | |
and |
68
60-63
Chrome disabled
SharedArrayBuffer on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This was a temporary removal while mitigations were put in place. |
79
16-17
Support was removed to mitigate speculative execution side-channel attacks (Windows blog).
|
78
57
Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog).
55-57
46-55
|
No |
No |
10.1-11.1 |
60-63
Chrome disabled
SharedArrayBuffer on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. |
60-63
Chrome disabled
SharedArrayBuffer on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. |
57
Support was disabled by default to mitigate speculative execution side-channel attacks (Mozilla Security Blog).
55-57
46-55
|
No |
10.3-11.3 |
No
Chrome disabled
SharedArrayBuffer on January 5, 2018 to help reduce the efficacy of speculative side-channel attacks. This is intended as a temporary measure until other mitigations are in place. |
See also
© 2005–2021 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics/and