diff options
| author | Bob Wilson <bob.wilson@apple.com> | 2009-08-29 05:53:25 +0000 |
|---|---|---|
| committer | Bob Wilson <bob.wilson@apple.com> | 2009-08-29 05:53:25 +0000 |
| commit | 502c35e863882790a94ad432d0a03c4a7e1a0aad (patch) | |
| tree | 7f6fb1bc27e09199241004cee240da39f60d633a /lib/CodeGen/AsmPrinter/DwarfException.cpp | |
| parent | 0ac7faa993d472be4a23e0e58fa6e9372960cfe8 (diff) | |
| download | external_llvm-502c35e863882790a94ad432d0a03c4a7e1a0aad.zip external_llvm-502c35e863882790a94ad432d0a03c4a7e1a0aad.tar.gz external_llvm-502c35e863882790a94ad432d0a03c4a7e1a0aad.tar.bz2 | |
PR4795: Remove EEVT::isFP, isInt and isVec types used by TableGen's type
inferencing. As far as I can tell, these are equivalent to the existing
MVT::fAny, iAny and vAny types, and having both of them makes it harder
to reason about and modify the type inferencing code.
The specific problem in PR4795 occurs when updating a vAny type to be fAny
or iAny, or vice versa. Both iAny and fAny include vector types -- they
intersect with the set of types represented by vAny. When merging them,
choose fAny/iAny to represent the intersection. This is not perfect, since
fAny/iAny also include scalar types, but it is good enough for TableGen's
type inferencing.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@80423 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/CodeGen/AsmPrinter/DwarfException.cpp')
0 files changed, 0 insertions, 0 deletions