[SelectionDAG] Use report_fatal_error instead of llvm_unreachable in some code that...
authorCraig Topper <craig.topper@intel.com>
Thu, 16 Nov 2017 06:02:03 +0000 (06:02 +0000)
committerCraig Topper <craig.topper@intel.com>
Thu, 16 Nov 2017 06:02:03 +0000 (06:02 +0000)
commit36e8d66e1ad8fb8da16733d072811b68bf26be00
treedd0ce38b1320f9f82a16cc4eecb555cb86a4203d
parent2f13e790839f1b3f975a254ffd4c29a171ab9204
[SelectionDAG] Use report_fatal_error instead of llvm_unreachable in some code that can be reached if targets don't configure things correctly.

For example, this is currently reachable by X86 if you use a masked store intrinsic with a v1iX type.

Using a fatal error seems like a better user experience if someone were to encounter this on a release build. There are several other similar places that have been converted from unreachable to fatal error previously.

llvm-svn: 318379
llvm/lib/CodeGen/SelectionDAG/LegalizeVectorTypes.cpp