amd64 Linux binary triggers SIGILL due to SSE4a instructions #3068
-
The |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
Are you using a prebuilt binary? If so, try the "portable" variants (they end with 'p' - e.g. qsvp, qsvlitep) as they are compiled with no CPU features enabled. Otherwise, compile from source on your machine with the "target-cpu=native" rustflag enabled so it will only enable CPU features available on your CPU. |
Beta Was this translation helpful? Give feedback.
-
|
I got the latest version through |
Beta Was this translation helpful? Give feedback.
-
|
And yes. running |
Beta Was this translation helpful? Give feedback.
-
|
Because its compiled with qsv/.github/workflows/publish.yml Lines 37 to 46 in 34154e6 |
Beta Was this translation helpful? Give feedback.
-
|
Then surely the pre-built binary zip file should not have the nomenclature x86_64 since it is no longer x86_64 and it is purely amd64 (and not even amd64 in a general sense!) Downloading qsv-9.1.0-x86_64-unknown-linux-musl.zip does not work on a frame.work intel 13th gen. If you're gonna call it x86_64 then be compatible with SSE4.1 / 4.2 etc. I feel that you've broken the principle of least surprise with this since there's no obvious 💥BREAKING CHANGE use qsvp if you're on an intel chip in the 5 / 6/ 7/ 8/ 9/ release notes. |
Beta Was this translation helpful? Give feedback.
Are you using a prebuilt binary? If so, try the "portable" variants (they end with 'p' - e.g. qsvp, qsvlitep) as they are compiled with no CPU features enabled.
Otherwise, compile from source on your machine with the "target-cpu=native" rustflag enabled so it will only enable CPU features available on your CPU.