-
Notifications
You must be signed in to change notification settings - Fork 166
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
Need to test Node on intel cpu that has no avx feature. #704
Comments
Any Intel CPU without AVX or just Skylake and above? I have an Ivy Bridge system that I'm reasonably sure has no AVX I could use to investigate. Is nodejs/node#12691 (comment) the test case to try? |
The issue was only confirmed on Intel Celeron N3350. I guess that it depends on the product name such as Celeron or Atom rather than the micro architecture name such as Skylake or Ivy Bridge. But it is worth while testing it other cpu if it does not support AVX. https://en.wikipedia.org/wiki/List_of_Intel_Celeron_microprocessors#.22Apollo_Lake.22_.2814_nm.29_2 shows that they do support up to SSE4.2 not AVX. Usually low-end note books or note pads have Celeron or Atom cpu wiht Windows. We have to look for someone who can build and test Node on such machines. |
@shigeki I have access to a |
@santigimeno That's great! Could you try to run a sample code of nodejs/node#12691 (comment) at first? Edit: Any version of Node is okay. |
@shigeki tested with
|
@santigimeno Thanks, but it is sad for me that we cannot reproduce the issue. Do you run it on Windows? |
No, its running a linux |
@santigimeno If possible, can you run the test it on Windows? |
@shigeki unfortunately that's not going to be possible. I think I have another old box with a different processor that doesn't support |
@santigimeno Thanks. The result that the testing on Linux is good is great help for me. |
I have an old (7 year old) machine with a Celeron. I'll give it a try... |
I have tested on a
|
For build infra purposes; can we emulate it by skipping flags and running qemu? |
@santigimeno Thanks for testing. For summarizing the current results, it shows that
It has a possibility that SHA extension on Windows causes the issue. |
It was confirmed that the issue is caused by building openssl with masm (Microsoft Assembler). |
Through the investigation of nodejs/node#12691 , Node seems to have sha256 hash computation failure on Intel CPU that has no avx feature.
This is a list of such CPU.
Unfortunately, I do not have the one and cannot make further investigation of the issue.
Is there any chance to have a machine that has above cpu?
The text was updated successfully, but these errors were encountered: