Add TYPE_FLAG_FUND_TYPE bit to the flags member of the type structure,
authorFred Fish <fnf@specifix.com>
Wed, 15 Apr 1992 05:42:00 +0000 (05:42 +0000)
committerFred Fish <fnf@specifix.com>
Wed, 15 Apr 1992 05:42:00 +0000 (05:42 +0000)
commit4a11eef2ebf99f527ee5452386a5f2a099ed6b8b
tree8a8e090f544dde28aaa060b49ac7c6eee14109b3
parente4b9dd935bd566dc1f46ee4c1a6f3c31755318d5
Add TYPE_FLAG_FUND_TYPE bit to the flags member of the type structure,
and use it to decide when to print the actual type name rather than
trying to invent the name of a fundamental type.  This clears up the
confusion between int/long when they are the same sizes, removes one
obstacle to multi-language support (previously valprint.c thought
everything was a C type), and allows gdb to support distinctions between
explicitly and implicitly signed types when the compiler supports such
distinction in the debug output (as does every ANSI compiler I tested
except for gcc).
gdb/ChangeLog
gdb/c-exp.y
gdb/gdbtypes.c
gdb/gdbtypes.h
gdb/m2-exp.y
gdb/mipsread.c
gdb/valprint.c