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

[Jay K]

1) Let's not be too quick to assume the new debugging stuff is correct.
  I just started it in August, in response to internal compiler errors passing records by value on SPARC64.
  (seems unrelated, but it isn't; there isn't really "debug" stuff in gcc backends, there are merely
  types in the trees, and we were creating records with size but not fields at all, pretty poor
  gcc citizens imho...)
  Though they probably often are correct. I know the level of indirection is sometimes wrong though, like
  on record parameters.

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.

 - Jay



----------------------------------------
> From: dragisha at m3w.org
> To: rodney_bates at lcwb.coop
> Date: Tue, 5 Oct 2010 22:58:54 +0200
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] m3gap.... what is it and what does this mean?
>
> It was same debugging path, but event is X event, so...
>
> On Tue, 2010-10-05 at 14:29 -0500, Rodney M. Bates wrote:
> > Are the gdb and m3gdb prints for the same value of 'event'? Several
> > of the fields show different
> > values.
> >
> > Dragiša Durić wrote:
> > > (gdb) p event
> --
> Dragiša Durić 
>