-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures and segfaults when building with Visual Studio 2022 compiler v14.38.33130 #222
Comments
@cgohlke Thanks for reporting this issue. Although I don't expect any difference, do earlier versions of zfp pass with 14.38.33130? It's possible that the data model is not detected properly, even though both compilers report LLP64. Can you please build with
and see if that fixes the issue? |
No, but I only tried with 1.0.0 and 1.0.1 git tags so far.
No, unfortunately not. |
zfp-0.5.5 passes with 14.38.33130
|
As a workaround, compile with the
|
Thanks for the suggestion. I doubt that we have access to the same compiler/OS/hardware setup, so debugging this from our end will be challenging. AppVeyor supports Visual Studio Community 2022 version 17.5.0. We can take a look and see if the issue can be reproduced with that compiler, though it seems unlikely as the issue seems confined to one particular compiler version and system. By the way, zfp 1.0.x is not ABI compatible with 0.5.y. I assume you've rebuilt any binaries that depend on zfp. |
Yes, it could be a compiler bug introduced by the latest VS update. This issue is meant as a "heads-up" in case someone else runs into it. The workaround, to build with
Sure, I was just rebuilding 0.5.5 temporarily for testing this issue. |
Heads-up: this may not be an issue with the ZFP source code, but I get many test failures when compiling zfp 1.0.1 from source with the current/latest Visual Studio 2022 compiler version 14.38.33130 on Windows 11. This is for the AMD64-bit build (32-bit and ARM64 pass):
CMake output
Reverting to the previous compiler version 14.37.32822 fixes the issue:
Most ZFP related tests in imagecodecs also fail or segfault when linked with zfp.lib compiled with the 14.38.33130 compiler.
The text was updated successfully, but these errors were encountered: