Displaying 2 results from an estimated 2 matches for "0e96dd1f".
2018 Sep 26
2
[FPEnv] FNEG instruction
...) are not the same operation. They are *very* similar, but still different at an edge case(s). The current transformations that occur in LLVM are unsafe.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180926/0e96dd1f/attachment.html>
2018 Sep 26
2
[FPEnv] FNEG instruction
Do we really want to have fneg be the only instruction with guaranteed no side effects? That just sounds like a gotcha waiting to happen. Or it could result in horrible code depending on the architecture.
I’m still leaning towards having both an intrinsic and an instruction, and if they happen to have the same behavior then that’s fine. If fneg is to be a special instruction with extra promises