-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Improve jpx decoding by around 20% in enabling simd support when compiling OpenJPEG #17983
Conversation
/botio test |
From: Bot.io (Windows)ReceivedCommand cmd_test from @calixteman received. Current queue size: 0 Live output at: http://54.193.163.58:8877/368b8497d3f05d7/output.txt |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @calixteman received. Current queue size: 0 Live output at: http://54.241.84.105:8877/78c62b0b48068c7/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.241.84.105:8877/78c62b0b48068c7/output.txt Total script time: 26.90 mins
Image differences available at: http://54.241.84.105:8877/78c62b0b48068c7/reftest-analyzer.html#web=eq.log |
From: Bot.io (Windows)FailedFull output at http://54.193.163.58:8877/368b8497d3f05d7/output.txt Total script time: 39.32 mins
Image differences available at: http://54.193.163.58:8877/368b8497d3f05d7/reftest-analyzer.html#web=eq.log |
Have you tested that the image decoder still works in Node.js environments with this change? |
No I didn't.
and it complains because of the wrong format but the wasm loaded, so it should be ok. |
I just wanted to check that the SIMD-part didn't break anything (we probably don't need specific Node.js tests here). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me, thank you!
No description provided.