taisel/IodineGBA

Don’t use atomic operations if we are already in a locked critical
section.

In case futexWait is checked at the same time by both threads, do a
compare and exchange on the store before the futexWait check.

Should help stabilize the web worker fps.

no more busy waiting, use futex sleeps instead. Also apparently web
worker usage now needs the cycle adjustment for over buffering enabled,
not just under.

SharedArrayBuffer + Atomics API is REQUIRED for web worker usage.
Otherwise it will default to the same thread generic version.

Eeeh, tell me how this goes...

We use it for sharing low latency buffer metrics.

Emulator run in a web worker while A/V output stuff is run in the main
thread.

Seems they dropped mozRequestAnimationSupport, so we couldn't sniff for
that anymore. That was causing us to draw graphics in a way firefox is
slow with.

Typo on function name. Was causing volume issues in Iridion 3D after
the optimization update recently.

Adding the remaining full 16 and 32 bit write and read optimizations.

continuing sound code touchup.

Enforcing some types better. Removed an unused variable. Mostly
enforcing double type logic where needed.

Trying to clean up the i/o tables and move some bit masking and shifts
into the target function calls.

Might as well use unsigned instead of signed int time logic...

Only generate date objects in glue code. Pass the current time via
timer callback as an integer instead. Use some settings values directly
rather than doing weird shit.