#10378: min/max for Double/Float instances are incorrect -------------------------------------+------------------------------------- Reporter: lerkok | Owner: Type: bug | Status: new Priority: high | Milestone: Component: Compiler | Version: 7.10.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by lerkok): @rwbarton: Ah, thanks for that pointer, I'm not sure if it's a true duplicate (I didn't see a discussion of +0/-0 in there); but the tickets are indeed related. Feel free to close/merge. I definitely agree that we need more discussion on this. Since the other one is closed, perhaps this one can stay. PS. I just found out that the min/max implementation in Intel CPU's actually do not follow the reference implementation I gave in the ticket precisely. I'll put a note in there. Something else to discuss on how to proceed. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10378#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler