This PR suggests a temporary workaround for a compiler bug introduced in Visual Studio 2022 version 17.12.
This workaround is required to fix the CI until the upstream compiler bug is resolved.
This PR suggests a temporary workaround for a compiler bug introduced in Visual Studio 2022 version 17.12.
This workaround is required to fix the CI until the upstream compiler bug is resolved.
Visual Studio 2022 version 17.12 introduced a bug that causes an
internal compiler error.
See: https://github.com/bitcoin/bitcoin/issues/31303.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31307.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | maflcko, TheCharlatan, brunoerg |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
lgtm ACK b2d536100282bd901d3e0be7f7f4a6966e0ef817
ACK b2d536100282bd901d3e0be7f7f4a6966e0ef817
ACK b2d536100282bd901d3e0be7f7f4a6966e0ef817
Can you link to your upstream bug report.
Can you link to your upstream bug report.
I haven’t reported this upstream yet, as I’ve been struggling to create minimal reproducible code.
I'd say this is fine to merge even without an upstream report. Even if there was one, it will take some time (weeks?) to propagate the fix. Blocking the CI for this repo on that seems not ideal.