https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128133
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
CC| |jakub at gcc dot gnu.org,
| |rdapp at gcc dot gnu.org
Last reconfirmed| |2026-10-26
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. So this is exposing "wrong" padding handling where we basically
assume that loads from memory materialize "correct" padding as if extended,
like we do for bool (the only previously handled case). For bitfields
we defer to ifcvt to expose BIT_FIELD_REFs.
The appropriate fix for now is to reject non-mode precision types that
we can backport and add proper support later.
There's odd type_mode_padding_p handling in vectorizable_load, but no
testcase, so I wonder what this was added for.
I have a patch plugging this at the load side. Is there a similar issue
on the store side? Testcase?
