-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Ensure that negation of floating-point values is correctly handled #105629
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
@@ -415,18 +430,7 @@ inline double EvaluateUnaryScalarSpecialized<double>(genTreeOps oper, double arg | |||
template <typename TBase> | |||
TBase EvaluateUnaryScalar(genTreeOps oper, TBase arg0) |
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.
nit: is EvaluateUnaryScalar
method needed then? callers can call EvaluateUnaryScalarSpecialized
directly
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.
It might not be needed, but it's consistent with the setup of other APIs.
If we were to change this, I'd probably make it EvaluateUnaryScalar
and just specialize that directly instead. That way there isn't two differently named entry points for Unary vs Binary vs ...
c21e11e
to
d4a0101
Compare
FYI @tannergooding about this regression: #106144 (also mentioned above) |
This resolves #105627