-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Verification failures on macos-14-arm64 #294
Comments
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 25, 2024
It's unclear to me if it should be `0` (SKIP) or just a value that is quite common across platforms and compilers. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 26, 2024
polymur Verification value 0xA612032C means that polymur_seed_init() was not called. Currently, polymur is compiled in unconditionally, so it should be initialized unconditionally as well. See rurban#294.
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 26, 2024
polymur Verification value 0xA612032C means that polymur_seed_init() was not called. Currently, polymur is compiled in unconditionally, so it should be initialized unconditionally as well. See rurban#294, rurban#296, rurban#297, rurban#298 and rurban#299.
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 26, 2024
Verification value 0x9FBDD2B1 for k-hashv32 and 0x70E67C61 for k-hashv64 signal, that the has was not properly seeded. Currently, k-hashv32 and k-hashv64 are compiled depending on HAVE_KHASHV from CMakeLists.txt, so initialization should be done depending on same macro as well. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It's not 100% clear to me if it's UB, CC bug or lack of some kind of memory barrier, but the very same quite innocent-looking code leads to different results on macos-arm64 platform and breaks nmhash32 See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It's unclear to me if it should be `0` (SKIP) or just a value that is quite common across platforms and compilers. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 polymur Verification value 0xA612032C means that polymur_seed_init() was not called. Currently, polymur is compiled in unconditionally, so it should be initialized unconditionally as well. See rurban#294, rurban#296, rurban#297, rurban#298 and rurban#299.
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 Verification value 0x9FBDD2B1 for k-hashv32 and 0x70E67C61 for k-hashv64 signal, that the has was not properly seeded. Currently, k-hashv32 and k-hashv64 are compiled depending on HAVE_KHASHV from CMakeLists.txt, so initialization should be done depending on same macro as well. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It's unclear to me if it should be `0` (SKIP) or just a value that is quite common across platforms and compilers. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 polymur Verification value 0xA612032C means that polymur_seed_init() was not called. Currently, polymur is compiled in unconditionally, so it should be initialized unconditionally as well. See rurban#294, rurban#296, rurban#297, rurban#298 and rurban#299.
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 Verification value 0x9FBDD2B1 for k-hashv32 and 0x70E67C61 for k-hashv64 signal, that the has was not properly seeded. Currently, k-hashv32 and k-hashv64 are compiled depending on HAVE_KHASHV from CMakeLists.txt, so initialization should be done depending on same macro as well. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It's not 100% clear to me if it's UB, CC bug or lack of some kind of memory barrier, but the very same quite innocent-looking code leads to different results on macos-arm64 platform and breaks nmhash32 See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It's unclear to me if it should be `0` (SKIP) or just a value that is quite common across platforms and compilers. See rurban#294
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 polymur Verification value 0xA612032C means that polymur_seed_init() was not called. Currently, polymur is compiled in unconditionally, so it should be initialized unconditionally as well. See rurban#294, rurban#296, rurban#297, rurban#298 and rurban#299.
darkk
added a commit
to darkk/smhasher
that referenced
this issue
Sep 27, 2024
It fixes arm builds, including macos-14-arm64 Verification value 0x9FBDD2B1 for k-hashv32 and 0x70E67C61 for k-hashv64 signal, that the has was not properly seeded. Currently, k-hashv32 and k-hashv64 are compiled depending on HAVE_KHASHV from CMakeLists.txt, so initialization should be done depending on same macro as well. See rurban#294
Merged
rurban
pushed a commit
that referenced
this issue
Sep 28, 2024
It's not 100% clear to me if it's UB, CC bug or lack of some kind of memory barrier, but the very same quite innocent-looking code leads to different results on macos-arm64 platform and breaks nmhash32 See #294
rurban
pushed a commit
that referenced
this issue
Sep 28, 2024
It's unclear to me if it should be `0` (SKIP) or just a value that is quite common across platforms and compilers. See #294
rurban
pushed a commit
that referenced
this issue
Sep 28, 2024
It fixes arm builds, including macos-14-arm64 Verification value 0x9FBDD2B1 for k-hashv32 and 0x70E67C61 for k-hashv64 signal, that the has was not properly seeded. Currently, k-hashv32 and k-hashv64 are compiled depending on HAVE_KHASHV from CMakeLists.txt, so initialization should be done depending on same macro as well. See #294
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
macOS Build highlights several verification failures:
superfast - Verification value 0x0C80403A ....... FAIL! (Expected 0x6306A6FE)
nmhash32 - Verification value 0x9905BCB1 ....... FAIL! (Expected 0x12A30553)
nmhash32x - Verification value 0x74B572DA ....... FAIL! (Expected 0xA8580227)
k-hashv32 - Verification value 0x9FBDD2B1 ....... FAIL! (Expected 0xB69DF8EB)
k-hashv64 - Verification value 0x70E67C61 ....... FAIL! (Expected 0xA6B7E55B)
polymur - Verification value 0xA612032C ....... FAIL! (Expected 0x4F894810)
The text was updated successfully, but these errors were encountered: