https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90109
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to nebiun from comment #3)
> Sorry, but the bug is not related to the wrong dimension of a type, but to
> the fact that the bitsize of the same type (K&R type: long, not long long or
> double or a user type) is showed as 32 bit as typedef and 64 bit if used in
> a structure.
Well, the typedef is "wrong" (but we can't do anything about that w/o
extensions) and the structure layout is "correct" (it seems we can
represent things there correctly).
What would be nice is to somehow not emit the bogus typedef but sth
that wouldn't show this mismatch. But I get that stabs doesn't have
a way to do this.
That said, dbxout.c might want to issue a warning if we emit "bogus"
stabs and suggest to use -gstabs+.
But I agree, you shouldn't use stabs. It's not maintained, the world
has moved on to dwarf (and I more than once argued to remove stabs support
from GCC).
