Pavel Roskin <proski@xxxxxxx> schrieb am 27.06.2007 07:01:22:
> On Tue, 2007-06-26 at 10:23 +0200, Thomas Schmid wrote:
> > Pavel Roskin <proski@xxxxxxx> schrieb am 13.06.2007 07:22:02:
>
> > > What happens is the base types like uchar_ctype, which are supposed
to
> > > be initialized once and never changed again, are actually
initialized by
> > > the first typedef, so they are sort of "imprinted" with the new
name.
> >
> > > And the code is:
> > >
> > > if (is_typedef) {
> > > if (base_type && !base_type->ident)
> > > base_type->ident = ident;
> > > } else if (base_type && base_type->type == SYM_FN) {
> > >
> >
> > If I get it right, every typedef pointing to a base type should lead
into
> > a new base type to get its right ident?
>
> I don't understand your question.
I see, sorry, i only meant that every typedef (pointing to a base type)
should get its own symbol->ctype->base_type with a new ident.
> My interpretation of the code is following. Types may have idents,
> which keep information where and how the type was defined. Base types
> don't have idents.
But unfortunately they get one.
Best regards.
Thomas Schmid
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
