Rework x64 addressing-mode lowering to be slightly more flexible. (by…

…tecodealliance#4080)

This PR refactors the x64 backend address-mode lowering to use an
incremental-build approach, where it considers each node in a tree of
`iadd`s that feed into a load/store address and, at each step, builds
the best possible `Amode`. It will combine an arbitrary number of
constant offsets (an extension beyond the current rules), and can
capture a left-shifted (scaled) index in any position of the tree
(another extension).

This doesn't have any measurable performance improvement on our Wasm
benchmarks in Sightglass, unfortunately, because the IR lowered from
wasm32 will do address computation in 32 bits and then `uextend` it to
add to the 64-bit heap base. We can't quite lift the 32-bit adds to 64
bits because this loses the wraparound semantics.

(We could label adds as "expected not to overflow", and allow *those* to
be lifted to 64 bit operations; wasm32 heap address computation should
fit this.  This is `add nuw` (no unsigned wrap) in LLVM IR terms. That's
likely my next step.)

Nevertheless, (i) this generalizes the cases we can handle, which should
be a good thing, all other things being equal (and in this case, no
compile time impact was measured); and (ii) might benefit non-Wasm
frontends.

Release Wasmtime 0.36.0 (bytecodealliance#4058)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

Release notes and version bumps for 0.35.3. (bytecodealliance#4014)

* Release notes for 0.35.3.

* Bumped all crate versions for Wasmtime 0.35.3 / Cranelift 0.82.3 patch release.

[automatically-tag-and-release-this-commit]

Release Wasmtime 0.35.2 (bytecodealliance#3985)

* Bump Wasmtime to 0.35.2

[automatically-tag-and-release-this-commit]

* Add release notes for 0.35.2

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Nick Fitzgerald <[email protected]>

Release Wasmtime 0.34.2 (bytecodealliance#3984)

* Bump Wasmtime to 0.34.2

[automatically-tag-and-release-this-commit]

* Add release notes for 0.34.2

* Disable stack overflow tests on Windows

This test is disabled on Windows because we determined it is too risky to back
port bytecodealliance#3861 to the 0.34.x
release branch.

* Switch back to windows-2019 on CI (bytecodealliance#3854)

Looks like windows-2022 is failing, let's perhaps pin for now?

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Nick Fitzgerald <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

Bump Wasmtime to 0.35.1 (bytecodealliance#3911)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

Bump Wasmtime to 0.35.0 (bytecodealliance#3885)

[automatically-tag-and-release-this-commit]

Co-authored-by: Wasmtime Publish <[email protected]>

Release Wasmtime 0.34.1 (bytecodealliance#3812)

* Bump Wasmtime to 0.34.1

[automatically-tag-and-release-this-commit]

* Update RELEASES for 0.34.1.

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Peter Huene <[email protected]>

Release Wasmtime 0.33.1 (bytecodealliance#3813)

* Bump Wasmtime to 0.33.1

[automatically-tag-and-release-this-commit]

* Update RELEASES for 0.33.1.

* Try to fix CI for Rust 1.58 (bytecodealliance#3689)

PATH lookup for WIndows command execution was tweaked slightly to not
search the cwd, so let's see if this fixes things...

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Peter Huene <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

Release Wasmtime 0.34.0 (bytecodealliance#3768)

* Bump Wasmtime to 0.34.0

[automatically-tag-and-release-this-commit]

* Add release notes for 0.34.0

* Update release date to today

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>