tree efe759a919d4cde1a0a9ec5566dcf4c5545dd694
parent 11f8919bd3661cbacc53b2bd57903253e085d7aa
author Craig Topper <craig.topper@intel.com> 1547146934 +0000
committer Craig Topper <craig.topper@intel.com> 1547146934 +0000

[X86] Simplify the BRCOND handling for FCMP_UNE.

Despite what the comment says, FCMP_UNE would be an OR not an AND. In the lowering code the first branch created still goes to the original destination. The second branch was exchanged to go to where the subsequent unconditional branch went. This is different than what we do for FCMP_OEQ where both branches that we create go to the original unconditional branch.

As far as I can tell, I think this means we don't need to exchange the branch target with the unconditional branch for FCMP_UNE at all.

Differential Revision: https://reviews.llvm.org/D56309

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@350873 91177308-0d34-0410-b5e6-96231b3b80d8