Changes between Version 4 and Version 5 of CompleteInteger


Ignore:
Timestamp:
May 7, 2014, 1:51:48 AM (5 years ago)
Author:
cameron
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CompleteInteger

    v4 v5  
    1414== Short Integer Types ==
    1515
    16 === Example: 2-bit Fields ===
     16Should the i1, i2, i4 types be legalized?   They seem to arise
     17in some SIMD operations such as the natural bitcast from <2 x i1> to i2.
    1718
    18 There can be some applications of 2-bit integer fields, i.e., the
    19 SIMD vector type <64 x i2> for 128-bit SIMD registers.
     19The I2Result bug needs to be addressed.
    2020
    21 Can this be implemented in a generic way as follows:
    22 
    23   1.  Make it a legal type in the SelectionDAG !LegalizeTypes phase.
    24   2.  Create implementations of the standard vector operations and rule out all others in the SelectionDAG Legalize phase.
    25   3.  Implement each operation using bitwise logic on the 2 positions of each field.
    26 
    27 We explore this possibility with the [wiki:i2Vector i2Vector] project.
     21Vectors of short integers may be more important than the short integers themselves.
    2822
    2923== Long Integer Project ==
     
    4135the BitShuffle subproject can be implemented.
    4236
     37=== Example: 2-bit Fields ===
     38
     39There can be some applications of 2-bit integer fields, i.e., the
     40SIMD vector type <64 x i2> for 128-bit SIMD registers.
     41
     42Can this be implemented in a generic way as follows:
     43
     44  1.  Make it a legal type in the SelectionDAG !LegalizeTypes phase.
     45  2.  Create implementations of the standard vector operations and rule out all others in the SelectionDAG Legalize phase.
     46  3.  Implement each operation using bitwise logic on the 2 positions of each field.
     47
     48We explore this possibility with the [wiki:i2Vector i2Vector] project.
     49
     50
    4351== Vectors of Long Integers ==
    4452