> I am not sure how to deal with this, given that we have mismatched > V_C_Es anyway, I'm inclined not to care and let the expander deal with > it. But at the same I understand that it is ugly and will certainly > cause somebody more headache in the future. I suppose that not > scalarizing here might hurt performance and would be frowned upon at > the very least. If the fields bigger than the record approach is the > standard way of doing this, perhaps SRA can detect such cases and > produce these strange COMPONENT_REFs instead, but is it so?
You may remember that we went that way before (building a COMPONENT_REF for bit-fields instead of fully lowering the access) so doing it again would be a step backwards. Likewise if we refuses to scalarize. So IMO it's either low- level fiddling in SRA or in the expander (my preference too). -- Eric Botcazou
