http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55195
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |middle-end --- Comment #9 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2012-11-05 16:20:44 UTC --- (In reply to comment #8) > That would be nice, and pretty straightforward to code, but we seem short of > generator program patches reviewers now. I take back that statement about this being straightforward. We need valid minimum and maximum instruction lengths. The opaque dummy clause automatically provides a value to be included in these calculations. If we had a varying_length attribute, I suppose we could make its value the maximum length, and 0 the minimum length. Maybe we should call the attribute max_length then. But something would need to be done to weave these values into the generated insn_ min / default _length functions.