search for: getsizeasvectorel

...nd of API to TTI that allows the default logic (# == > > vector-size/type-size) to be overridden. This could be something > > specific to the problem at hand, such as: bool > > areFloatsStoredAsDoublesInVectors(), or something more general. > > Maybe something like: unsigned getSizeAsVectorElement(Type *T) > > which would return the number of bytes that the specified type > > actually takes up when used as a vector element. > > I prefer to fix the cost model. Do you see any problems with this > approach ? I understand that it is more difficult to select the VF &gt...

...y compile-time increase. 2. Add some kind of API to TTI that allows the default logic (# == vector-size/type-size) to be overridden. This could be something specific to the problem at hand, such as: bool areFloatsStoredAsDoublesInVectors(), or something more general. Maybe something like: unsigned getSizeAsVectorElement(Type *T) which would return the number of bytes that the specified type actually takes up when used as a vector element. I'm certainly open to suggestions. I don't know if this situation applies to other targets as well. Thanks again, Hal -- Hal Finkel Postdoctoral Appointee Leader...

...TTI that allows the default logic (# == >>> vector-size/type-size) to be overridden. This could be something >>> specific to the problem at hand, such as: bool >>> areFloatsStoredAsDoublesInVectors(), or something more general. >>> Maybe something like: unsigned getSizeAsVectorElement(Type *T) >>> which would return the number of bytes that the specified type >>> actually takes up when used as a vector element. >> >> I prefer to fix the cost model. Do you see any problems with this >> approach ? I understand that it is more difficult to...

...or <8 x i8>. > 2. Add some kind of API to TTI that allows the default logic (# == vector-size/type-size) to be overridden. This could be something specific to the problem at hand, such as: bool areFloatsStoredAsDoublesInVectors(), or something more general. Maybe something like: unsigned getSizeAsVectorElement(Type *T) which would return the number of bytes that the specified type actually takes up when used as a vector element. I prefer to fix the cost model. Do you see any problems with this approach ? I understand that it is more difficult to select the VF in the BB vectorizer, but I suspect th...