Add I128 atomic support to the x64 backend

[beetrees]

Rust is currently in the process of stabilising 128-bit atomics (rust-lang/rust#99069 (comment)), but Cranelift (and therefore rustc_codegen_cranelift) doesn't currently support 128-bit atomics.

This PR adds IR support for 128-bit atomics and implements lowering them for the x64 backend using cmpxchg16b.

[github-actions]

Subscribe to Label Action

cc @cfallin, @fitzgen

This issue or pull request has been labeled: "cranelift", "cranelift:area:x64", "cranelift:meta", "fuzzing", "isle", "wasmtime:api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

• cfallin: isle
• fitzgen: fuzzing, isle

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

[github-actions]

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

• If you added a new Config method, you wrote extensive documentation for
  it.

  Our documentation should be of the following form:

  Short, simple summary sentence.
  
  More details. These details can be multiple paragraphs. There should be
  information about not just the method, but its parameters and results as
  well.
  
  Is this method fallible? If so, when can it return an error?
  
  Can this method panic? If so, when does it panic?
  
  # Example
  
  Optional example here.
  

• If you added a new Config method, or modified an existing one, you
  ensured that this configuration is exercised by the fuzz targets.

  For example, if you expose a new strategy for allocating the next instance
  slot inside the pooling allocator, you should ensure that at least one of our
  fuzz targets exercises that new strategy.

  Often, all that is required of you is to ensure that there is a knob for this
  configuration option in wasmtime_fuzzing::Config (or one
  of its nested structs).

  Rarely, this may require authoring a new fuzz target to specifically test this
  configuration. See our docs on fuzzing for more details.

• If you are enabling a configuration option by default, make sure that it
  has been fuzzed for at least two weeks before turning it on by default.

---

To modify this label's message, edit the .github/label-messager/wasmtime-config.md file.

To add new label messages or remove existing label messages, edit the
.github/label-messager.json configuration file.

Learn more.

[fitzgen]

Very nice, thanks!

[beetrees]

I think CI might be stuck? Test macOS x86_64 (wasmtime-cli) seems to have been stuck on cargo fetch --locked for over an hour.

[beetrees]

Never mind, it's managed to move on to the next step.

[beetrees]

It seems to have got stuck in the ./ci/run-tests.sh step now (first it was stuck at the very start of the step for around 30 mins, and now it's stuck at Compiling bytesize v1.3.0).