-
Notifications
You must be signed in to change notification settings - Fork 319
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
Build failing on various EMU128 tests #2375
Comments
I am able to get all of the tests in hwy/tests in the master branch to pass successfully with Visual C++ 2022 on the EMU128 target on both x86 and x86_64 with the fixes I made to hwy/tests/hwy_gtest.h in pull request #2376. The HWY_EMU128 and HWY_SCALAR targets can also be disabled by passing Google Highway needs to be updated to the latest commit of the master branch (which is currently commit 28c442f) to fix the build failure issues with various EMU128 tests with Visual C++. |
Also implemented a fix in pull request #2377 to fix a linker error in bench_sort if HWY_TEST_STANDALONE is 1. |
Thanks for the reply! Yea indeed that fixes the issue. With the latest commit on the master branch everything compiles fine for me. |
Thank you @johnplatts ! |
Hey all,
I'm trying to set up a pipeline for automating building highway when needed, but I keep running into EMU128 tests related build errors. I'm building on cmake 3.31.0 with the following parameters:
and then
This is on a fresh install of cmake 3.31.0 and highway 1.2.0, on windows 11, with an amd 5900X.
This results in EMU128 errors on the test at various places. Some examples:
These last two I'm not 100% sure are related, but just in case:
I've tried skipping the testing portions of the cmake by removing gtest references like the documentation says, and also by trying to remove any HWY_TEST_FILES files. Both result in the cmake "succeeding", but no export when dumpbin-ing the hwy.lib.
I've also tried passing /O2 flags and the cl.exe compiler to the cmake options (among various other tests), but this changes nothing. Any suggestions?
The text was updated successfully, but these errors were encountered: