Robin Dapp via Gcc-patches <gcc-patches@gcc.gnu.org> writes: >> It's not just a question of which byte though. It's also a question >> of which bit. >> >> One option would be to code-generate for even X and for odd X, and select >> between them at runtime. But that doesn't scale well to 2+2X and 1+1X. >> >> Otherwise I think we need to treat the bit position as a variable, >> with bitpos % 8 and bitpos / 8 being calculated at runtime. > > Thanks. I worked around it with a backend vec_extract<VNxBI>QI expander > so we don't run into that situation directly anymore. The problem is of > course still latent and I'm going to look at it again after some other things > on my plate.
Yeah, sounds like a good workaround. If the target has an efficient way of coping with the VLAness then the optab will probably be better than whatever the generic code ends up being. Thanks, Richard
