search for: dbf52d89

But this is another case. LLVM IR distinguishes between ordered and unordered compare and X86 backend has appropriate instructions. But during DAG selection we just lose this information and always generate unordered fcmp. I.e. in case of ordered fcmp the vcomiss should be generated, and in case of unordered - vucomiss. - Elena -----Original Message----- From: Dr D. Chisnall [mailto:dc552 at

...that C can expose, but normal fcmp instructions aren't the place for that. Tim. -------------- next part -------------- A non-text attachment was scrubbed... Name: tmp.c Type: text/x-csrc Size: 344 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130829/dbf52d89/attachment.c>

On 29 Aug 2013, at 08:19, Tim Northover <t.p.northover at gmail.com> wrote: > If so, a compare that used that instruction would have to become more > like an "invoke" with a landingpad for the exception and so on, > wouldn't it? The current fcmp can already distinguish between ordered > and unordered, because ucomiss provides that information. There are currently