For clarity's sake, the T in TQI is for "Three", right? [3 * 8 = 24]
Yep. I guess I could also call it PSImode by analogy to GCC.
I've been thinking that while QI,HI,SI,DI are clear, any other similarly
named modes might become problematic over time.
An alternative is I24 of course, but if one goes that route one needs to
resolve what to do about QI,etc.
[They *could* become aliases of I8, etc. and perhaps eventually be
removed entirely, at least from the application independent core.
Anything related to gcc may certainly want to use them.] This route has
the benefit of solving this problem for future weird architectures.
[And just because we add I24 doesn't mean we'd have to immediately add
all the others, e.g. I23, etc.]
Well, the most flexible option I think would be to implement the equivalent
of BITS_PER_UNIT and have the QI/HI/SI/DI modes adjust to match, maybe. I'm
really new to this and don't fully understand how modes are used in cgen yet,
but if it's ever a long-term goal to be able to cgen parts of the GCC backend,
it would be handy to mirror the same storage-layout abilities.