aboutsummaryrefslogtreecommitdiffstats
path: root/lib/CompilerDriver/CompilationGraph.cpp
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2009-04-18 20:16:54 +0000
committerDuncan Sands <baldrick@free.fr>2009-04-18 20:16:54 +0000
commit6a3a01eb07a391628766d95b3c4baeb3802b5b96 (patch)
tree29d0c808adeb32fa9b508ee757582fc28b6e32de /lib/CompilerDriver/CompilationGraph.cpp
parentd4c842fb66579a9f28ef122b08a7fad6560f3203 (diff)
downloadexternal_llvm-6a3a01eb07a391628766d95b3c4baeb3802b5b96.zip
external_llvm-6a3a01eb07a391628766d95b3c4baeb3802b5b96.tar.gz
external_llvm-6a3a01eb07a391628766d95b3c4baeb3802b5b96.tar.bz2
Don't try to make BUILD_VECTOR operands have the same
type as the vector element type: allow them to be of a wider integer type than the element type all the way through the system, and not just as far as LegalizeDAG. This should be safe because it used to be this way (the old type legalizer would produce such nodes), so backends should be able to handle it. In fact only targets which have legal vector types with an illegal promoted element type will ever see this (eg: <4 x i16> on ppc). This fixes a regression with the new type legalizer (vec_splat.ll). Also, treat SCALAR_TO_VECTOR the same as BUILD_VECTOR. After all, it is just a special case of BUILD_VECTOR. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@69467 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/CompilerDriver/CompilationGraph.cpp')
0 files changed, 0 insertions, 0 deletions