On 2013-04-18 16:58 , Hendrik Greving wrote:
Hi,
this is w.r.t. an older GCC version, I took a quick look and it looks
like it's still roughly the same in recent GCC's.
In function c-decl.c:grokdeclarator: I am debugging something and am
wondering, what does an IDENTIFIER_POINTER (id->identifie
Hi,
this is w.r.t. an older GCC version, I took a quick look and it looks
like it's still roughly the same in recent GCC's.
In function c-decl.c:grokdeclarator: I am debugging something and am
wondering, what does an IDENTIFIER_POINTER (id->identifier.id.str)
contain? I see long strings in there,
> So for an example, Ada layouts the records themselves and some times
> has a different order of the fields than the layouted offsets.
The Ada compiler uses stor-layout.c by default, like all the other compilers.
It does its own layout only when it has nothing to do, i.e. when the user has
speci
On Tue, 2009-06-23 at 20:52 -0700, Andrew Pinski wrote:
> On Tue, Jun 23, 2009 at 8:48 PM, Jerry Quinn wrote:
> > Hi, folks,
> >
> > I'm having trouble seeing how layout is specified at the GENERIC level
> > for RECORD_TYPEs. The docs and comments in tree.def say that you cannot
> > rely on the or
On Tue, Jun 23, 2009 at 8:48 PM, Jerry Quinn wrote:
> Hi, folks,
>
> I'm having trouble seeing how layout is specified at the GENERIC level
> for RECORD_TYPEs. The docs and comments in tree.def say that you cannot
> rely on the order of fields of the type. In stor-layout.c,
> layout_types() seems
Hi, folks,
I'm having trouble seeing how layout is specified at the GENERIC level
for RECORD_TYPEs. The docs and comments in tree.def say that you cannot
rely on the order of fields of the type. In stor-layout.c,
layout_types() seems to do the obvious thing, taking the fields in
order, but the d
