[LLVMdev] Boolean floats and v4i1

[Hal Finkel]

On Mon, 25 Jun 2012 05:45:57 +0000
"Rotem, Nadav" <nadav.rotem at intel.com> wrote:

> Hi Hal, 
> 
> Why do say that the type v4i64 is broken ?  You can specify that this
> type has no legal operations and the codegen will lower ("legalize")
> them to something  that works on your platform.  

For example, the AND operation is really only an AND operation on the
sign bits of the underlying floating-point numbers, it does not AND all
of the bits (and it always changes them so that the operation always
returns -1.0 or 1.0). But I need this AND to be used for the promoted
v4i1 values (so I need to mark it as legal and match it to the
associated vector logical operation).

Thanks again,
Hal

> 
> Nadav
> 
> 
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu
> [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Hal Finkel Sent:
> Monday, June 25, 2012 06:28 To: LLVM Developers Mailing List
> Subject: [LLVMdev] Boolean floats and v4i1
> 
> Hello,
> 
> I'm working on support for the SIMD instruction set on our new BG/Q
> supercomputer. This instruction set is v4f64 (with the exception of
> some int <-> fp conversions, floating-point only). The vectorized
> comparisons, logical operations and selects also exclusively use
> floating-point inputs. For those inputs that are logically vectors of
> booleans the system uses the following convention: positive numbers
> are true, everything else (including NaNs) are false. The outputs of
> logical operations are -1.0 and 1.0.
> 
> I am not sure how to best support this in LLVM. LLVM does not have an
> MVT::v4i1. One thing that I can do (without modifying LLVM core) is
> to add v4i64 to the vector registers, and pretend that the v4i1 is
> being promoted to that type (I match loads and stores to pairs of
> memory operations and fp<->int conversions). This works somewhat
> (CodeGen will happily generate vectorized selects, comparisons and
> logical ops on the comparison results), but leaves me with a broken
> v4i64 type (it is broken because the operations defined on that type
> only essentially respect the sign bit of the numbers -- so long as
> these are used only for the promoted v4i1 operations almost
> everything is fine, but these operations are not true v4i64
> operations).
> 
> What should I do here? Should I add MVT::v?i1 types so that they can
> be directly used without promotion?
> 
> Thanks again,
> Hal
> 
> --
> Hal Finkel
> Postdoctoral Appointee
> Leadership Computing Facility
> Argonne National Laboratory
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 



-- 
Hal Finkel
Postdoctoral Appointee
Leadership Computing Facility
Argonne National Laboratory