You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can I disable this when compiling node somehow? I only found this but this did not help. Or should I edit deps/v8/src/base/cpu.h and some more files directly?
What is the expected behavior? Why is that the expected behavior?
It is expected that "npm run build" succeeds on all CPU including older CPUs without AVX support.
The text was updated successfully, but these errors were encountered:
karussell
changed the title
Node crashes with 'illegal instruction' on old CPUs without AVX support like AMD Opteron 23xx or AMD FX-8300
Node crashes with 'illegal instruction' on old CPUs without AVX support like AMD Opteron 23xx
Jul 8, 2023
I'm fairly sure V8 conflates AVX with SSE3 in several places, meaning it assumes AVX is supported when SSE3 is. Fixes for that should go upstream, we won't carry out-of-tree V8 patches.
But check the stack trace in gdb first. Maybe the offending instruction originates somewhere else.
Version
20.4.0 or 16.20.1
Platform
Debian 11
Subsystem
No response
What steps will reproduce the bug?
Find the appropriate hardware and then:
=>
How often does it reproduce? Is there a required condition?
Can be only reproduced on hardware with a AMD Opteron 23xx (Gen 3 Class Opteron).
See this thread for more context. The underlying problem is highly likely that the CPUs have no AVX support.
Unfortunately disabling avx functionality does not seem to work
Can I disable this when compiling node somehow? I only found this but this did not help. Or should I edit deps/v8/src/base/cpu.h and some more files directly?
What is the expected behavior? Why is that the expected behavior?
It is expected that "npm run build" succeeds on all CPU including older CPUs without AVX support.
What do you see instead?
npm crashes with just "Illegal instruction".
Additional information
Related to #704 and RocketChat/Rocket.Chat#23938
The text was updated successfully, but these errors were encountered: