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
Could round rather than truncate in compileClampDoubleToByte? #16609
Could round rather than truncate in compileClampDoubleToByte? #16609
Conversation
EWS run on previous version of this PR (hash 88ed1fc) |
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
88ed1fc
to
ee94e3c
Compare
EWS run on current version of this PR (hash ee94e3c) |
Merging despite the build/test failures for mips and armv7 per request of @jjgriego |
https://bugs.webkit.org/show_bug.cgi?id=72054 rdar://113734964 Reviewed by Yusuke Suzuki. Right now there's a difference between our non-optimizing code and our C++ code for ClampedUint8Arrays. In the C++ code we correctly do a round to nearest (ties to even) but in the optimizing JITs we do a round to inifinity. This patch fixes our optimizing code to round to nearest too. * Source/JavaScriptCore/dfg/DFGSpeculativeJIT.cpp: (JSC::DFG::clampDoubleToByte): (JSC::DFG::compileClampDoubleToByte): * Source/JavaScriptCore/ftl/FTLLowerDFGToB3.cpp: (JSC::FTL::DFG::LowerDFGToB3::compileCompareStrictEq): Canonical link: https://commits.webkit.org/267100@main
ee94e3c
to
c55d067
Compare
Committed 267100@main (c55d067): https://commits.webkit.org/267100@main Reviewed commits have been landed. Closing PR #16609 and removing active labels. |
c55d067
ee94e3c