-
Notifications
You must be signed in to change notification settings - Fork 566
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
Errno error on windows/cygwin #18025
Labels
Comments
atoomic
added a commit
to atoomic/perl5
that referenced
this issue
Aug 3, 2020
Fix Perl#18025 This is fixing these two errors under windows: "Never use <avx512bwintrin.h> directly; include <immintrin.h> instead." "Never use <avx512vpopcntdqvlintrin.h> directly; include <immintrin.h> instead."
atoomic
added a commit
to atoomic/perl5
that referenced
this issue
Aug 3, 2020
Fix Perl#18025 This is fixing these two errors under windows: "Never use <avx512bwintrin.h> directly; include <immintrin.h> instead." "Never use <avx512vpopcntdqvlintrin.h> directly; include <immintrin.h> instead."
atoomic
added a commit
to atoomic/perl5
that referenced
this issue
Aug 28, 2020
Fix Perl#18025 This is fixing these two errors under windows: "Never use <avx512bwintrin.h> directly; include <immintrin.h> instead." "Never use <avx512vpopcntdqvlintrin.h> directly; include <immintrin.h> instead."
atoomic
added a commit
that referenced
this issue
Sep 14, 2020
Fix #18025 This is fixing these two errors under windows: "Never use <avx512bwintrin.h> directly; include <immintrin.h> instead." "Never use <avx512vpopcntdqvlintrin.h> directly; include <immintrin.h> instead."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed this error while parsing the CI log for a windows runner
full log available at https://pipelines.actions.githubusercontent.com/StwKAELrIIfJZjsjvFeJdim2u3AOp8ez6qvldOETh5vCDDWoz5/_apis/pipelines/1/runs/305/signedlogcontent/24?urlExpires=2020-08-03T04%3A56%3A23.5820001Z&urlSigningMethod=HMACV1&urlSignature=gbS4rY1tn8pCqAYy5pW3xLRld2r6pQOEIaKaAgW4PwQ%3D
I think we can also find the error/warnings from the most recent runs
suggested patch
The text was updated successfully, but these errors were encountered: