Re: What integer C type to use

Paul A. Clayton wrote:

On 3/13/24 3:24 PM, MitchAlsup1 wrote:

Stefan Monnier wrote:

[snip]

So, short vectors have a fairly free hand at shuffling data across their
vector (e.g. bitmatrix transpose), and they can be
implemented/scheduled/dispatched just like any other instruction, but
the vector length tends to be severely limited and exposed all over
the place.

 Consuming OpCode space like nobody's business.

Is that necessarily the case? Excluding the shuffle operations, I
think only loads and stores would need to have length specifiers.

Add signed byte add unsigned byte, add signed half, add unsigned half
add signed int, add unsigned int, add long, add 2 floats, add double
compared to ADD integer, add float and add double.
And then there is the addsub group, too.
I may be possible to avoid OpCode explosion, but neither x86, nor ARM
got anywhere close to avoiding the deluge of OpCodes.