Skip to content
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

apply arm64 windows workaround only on older version msvc #1121

Merged

Conversation

Changqing-JING
Copy link
Contributor

@Changqing-JING Changqing-JING commented Jan 8, 2024

The arm_neo.h bug of msvc is fixed. So that the workaround is not needed on new msvc

@Changqing-JING Changqing-JING force-pushed the remove_arm64_windows_work_around branch from f8a78e1 to a65d98d Compare January 8, 2024 05:31
#define vsqaddd_u64(src1, src2) neon_usqadds64(__uint64ToN64_v(src1), __int64ToN64_v(src2)).n64_u64[0]
#if (defined _MSC_VER) && (_MSC_VER < 1938)
#pragma message ("_MSC_VER value is: " _CRT_STRINGIZE(_MSC_VER))
#error "due to the bug of MSVC, this current version of visual studio is not supported. Please update. See https://developercommunity.visualstudio.com/t/In-arm64_neonh-vsqaddb_u8-vsqaddh_u16/10271747?sort=newest"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR. Can we keep the workaround for old versions of MSVC and issue a warning?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, changed as your idea

@Changqing-JING Changqing-JING force-pushed the remove_arm64_windows_work_around branch from a65d98d to cbcbb50 Compare January 8, 2024 08:25
@Changqing-JING Changqing-JING changed the title remove arm64 windows workaround apply arm64 windows workaround only on older version msvc Jan 8, 2024
@Changqing-JING
Copy link
Contributor Author

@mr-c why can emscripten test fail on this PR? This PR should not be related to emscripten

@mr-c
Copy link
Collaborator

mr-c commented Jan 8, 2024

@mr-c why can emscripten test fail on this PR? This PR should not be related to emscripten

The emscripten tests use the latest "tip-of-tree" build of emcc/clang to catch issues early. So it wasn't your change, but their change. Next we need to see if the stable emsdk version also fails, and if not, to switch to that from the "tot" version. Simultaneously we should file an issue with the emscripten people

@mr-c
Copy link
Collaborator

mr-c commented Jan 8, 2024

This might be the cause, so hopefully we can try again when the fix is released

emscripten-core/emscripten#21026

@mr-c mr-c merged commit 14311d6 into simd-everywhere:master Jan 12, 2024
75 of 76 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants