[all-commits] [llvm/llvm-project] fc4020: [X86] Mark fp128 FMA as LibCall instead of Expand....

topperc via All-commits all-commits at lists.llvm.org
Thu Nov 21 18:32:03 PST 2019


  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: fc4020dbbe446c6ba73fdda56390ce062eaf8f2e
      https://github.com/llvm/llvm-project/commit/fc4020dbbe446c6ba73fdda56390ce062eaf8f2e
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2019-11-21 (Thu, 21 Nov 2019)

  Changed paths:
    M llvm/lib/Target/X86/X86ISelLowering.cpp
    M llvm/test/CodeGen/X86/fp128-libcalls-strict.ll

  Log Message:
  -----------
  [X86] Mark fp128 FMA as LibCall instead of Expand. Add STRICT_FMA as well.

The Expand code would fall back to LibCall, but this makes it
more explicit.


  Commit: b29e5cdb7c98c93e16955e58efeb922da93f969f
      https://github.com/llvm/llvm-project/commit/b29e5cdb7c98c93e16955e58efeb922da93f969f
  Author: Craig Topper <craig.topper at intel.com>
  Date:   2019-11-21 (Thu, 21 Nov 2019)

  Changed paths:
    M llvm/lib/Target/X86/X86ISelLowering.cpp
    M llvm/test/CodeGen/X86/fp128-libcalls-strict.ll

  Log Message:
  -----------
  [X86] Add test cases for most of the constrained fp libcalls with fp128.

Add explicit setOperation actions for some to match their none
strict counterparts. This isn't required, but makes the code
self documenting that we didn't forget about strict fp. I've
used LibCall instead of Expand since that's more explicitly what
we want.

Only lrint/llrint/lround/llround are missing now.


Compare: https://github.com/llvm/llvm-project/compare/6bbca3411b38...b29e5cdb7c98


More information about the All-commits mailing list