Marijn Suijten

> In `ci.yml`, we have (twice): > > ``` > - if: ${{ matrix.target == 'aarch64-pc-windows-msvc' }} > run: | > echo "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\Llvm\x64\bin" >> $GITHUB_PATH >...

In this PR I added `/std:c11` and it's clearly visible in the CLI args for `clang-cl`, yet it keeps failing with a bunch of warnings indicating that `c11` support wasn't...

Regarding availability of `clang-cl` again, I was experimenting with our Debian bookworm runner image (Linux), and it doesn't provide `clang-cl` from neither the `llvm-15` nor the `clang-15` package, you need...

I gleaned the idea to apply the `-Wno-*` flags **that I already had in this PR** exclusively to `clang-cl` from https://github.com/briansmith/ring/pull/2727 (so that we don't break existing `cl.exe` invocations), but...

@briansmith is there anything we can do to further this PR? I could rebase it if it helps, but there are no conflicts at the moment.

That would be lovely. In the end I managed to bisect the problem (reverse GitHub issue link above), ~though can no longer find the quoted exact wording in the spec...

Thanks @spencer-lunarg! I haven't looked too closely at your PR, and don't have access to the machine today (it was specific interplay between Linux+Nvidia, using RenderDoc on o3de), but in...

@AlexRouSg it does not, as said above. This has nothing to do with "being reported by `vkGetPhysicalDeviceFeatures2`" because the caller _specifies what it wants to query_. --- When talking about...

Yes, that's what I was already requesting / suggesting above. The proposed PR definitely addresses something that I have wanted to have before, but wouldn't have found this issue that...

@Emilgardis thanks, so it's `buildx` that doesn't support Windows just yet. What's the right way to use this `cross` project for an `aarch64-pc-windows-msvc` target? As far as I'm aware Docker...