[M3devel] m3gap.... what is it and what does this mean?

[Dragiša Durić]

They are nice as they are, as long as debugging works. Information on
alignment is good to have.

On Tue, 2010-10-05 at 22:53 +0000, Jay K wrote:
> 2) The numbers are bit offset and bit size, so not as big as you might
> think.
> I can make them trivially byte offsets, if they are multiples of 8, at
> the cost
> of possible confusion when they aren't.
> Or they can just be called _m3gap1, _m3gap2, numbered either per-unit
> or per-type.
> 
> I could also try not putting them in at all, but merely bumping the
> offset
> of the next field in the same way as current and hoping backend
> doesn't relayout and move them toward the start. 
-- 
Dragiša Durić <dragisha at m3w.org>