summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/AMDGPU
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@gmail.com>2017-03-17 06:00:01 +0000
committerCraig Topper <craig.topper@gmail.com>2017-03-17 06:00:01 +0000
commitc1338f21ed8f3f06067b058914ad05ee2abeb7e5 (patch)
tree0b614cd48b00225d4a33b5898cbf4371ccf21b21 /llvm/lib/Target/AMDGPU
parent30c89eeeb69079a92f5afdce57fb2b2787d87b78 (diff)
downloadbcm5719-llvm-c1338f21ed8f3f06067b058914ad05ee2abeb7e5.tar.gz
bcm5719-llvm-c1338f21ed8f3f06067b058914ad05ee2abeb7e5.zip
[X86] Use update_llc_test_checks.py to regenerate a test and add command lines to demonstrate that we don't pick EVEX encoded instruction when AVX512 and FMA3 are both enabled.
This bug only exists on the scalar llvm.fma instrinsics. Looks like we don't test the llvm.fma intrinsics very thoroughly. In fact I don't see any tests for the vector versions. llvm-svn: 298045
Diffstat (limited to 'llvm/lib/Target/AMDGPU')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud