Displaying 4 results from an estimated 4 matches for "getsequentialnumel".
2020 Mar 09
8
[RFC] Refactor class hierarchy of VectorType in the IR
...s would be a fairly simple change, and we have a prototype implementation up at https://reviews.llvm.org/D75660 (Remove CompositeType class)
* Pros: Removing CompositeType would simplify the type hierarchy. Leaving SequentialType in would simplify some code and be more typesafe than having a getSequentialNumElements on Type.
* Cons: The value of SequentialType has also been called into question. If we wanted to remove it, now would be a good time. Conversion functions add complexity to the design. Introduces additional casting from Type.
3. Remove CompositeType and SequentialType. Roll the func...
2020 Apr 22
2
[Update][RFC] Refactor class hierarchy of VectorType in the IR
...s would be a fairly simple change, and we have a prototype implementation up at https://reviews.llvm.org/D75660 (Remove CompositeType class)
* Pros: Removing CompositeType would simplify the type hierarchy. Leaving SequentialType in would simplify some code and be more typesafe than having a getSequentialNumElements on Type.
* Cons: The value of SequentialType has also been called into question. If we wanted to remove it, now would be a good time. Conversion functions add complexity to the design. Introduces additional casting from Type.
3. Remove CompositeType and SequentialType. Roll the func...
2020 May 05
2
[Update][RFC] Refactor class hierarchy of VectorType in the IR
...a
> fairly simple change, and we have a prototype implementation up at
> https://reviews.llvm.org/D75660 (Remove CompositeType class)
>
> Pros: Removing CompositeType would simplify the type hierarchy. Leaving SequentialType in would simplify some code and be more typesafe than having a getSequentialNumElements on Type.
> Cons: The value of SequentialType has also been called into question. If we wanted to remove it, now would be a good time. Conversion functions add complexity to the design. Introduces additional casting from Type.
>
> Remove CompositeType and SequentialType. Roll the func...
2020 May 21
3
[RFC] Refactor class hierarchy of VectorType in the IR
...hat this would be a fairly simple change, and we have a prototype implementation up at https://reviews.llvm.org/D75660 (Remove CompositeType class)
* Pros: Removing CompositeType would simplify the type hierarchy. Leaving SequentialType in would simplify some code and be more typesafe than having a getSequentialNumElements on Type.
* Cons: The value of SequentialType has also been called into question. If we wanted to remove it, now would be a good time. Conversion functions add complexity to the design. Introduces additional casting from Type.
3. Remove CompositeType and SequentialType. Roll the functions dire...