When promoting the result of fp_to_uint/fp_to_sint,
authorDuncan Sands <baldrick@free.fr>
Mon, 10 Nov 2008 17:28:30 +0000 (17:28 +0000)
committerDuncan Sands <baldrick@free.fr>
Mon, 10 Nov 2008 17:28:30 +0000 (17:28 +0000)
commita29c13086a3add78a3a79f744573fe09eaa9dc88
tree2cfcdeb4398e87584b879bb62bc37ce65e0a740e
parentc04b6917c184ca9d6c7bc0c749a734f89cebcd35
When promoting the result of fp_to_uint/fp_to_sint,
inform the optimizers that the result must be zero/
sign extended from the smaller type.  For example,
if a fp to unsigned i16 is promoted to fp to i32,
then we are allowed to assume that the extra 16 bits
are zero (because the result of fp to i16 is undefined
if the result does not fit in an i16).  This is
quite aggressive, but should help the optimizers
produce better code.  This requires correcting a
test which thought that fp_to_uint is some kind
of truncation, which it is not: in the testcase
(which does fp to i1), either the fp value converts
to 0 or 1 or the result is undefined, which is
quite different to truncation.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@58991 91177308-0d34-0410-b5e6-96231b3b80d8
lib/CodeGen/SelectionDAG/LegalizeIntegerTypes.cpp
test/CodeGen/X86/trunc-to-bool.ll