diff options
| author | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2016-09-06 17:29:15 +0200 |
|---|---|---|
| committer | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2016-09-06 17:29:15 +0200 |
| commit | a9ff5f12cff6cd06f74ecf387ac5468984c94c6f (patch) | |
| tree | 020d432b910dacca794b4b486327d4e40b36c902 /gdb/infcall.c | |
| parent | 19f392bc2a93d9e64d063b884cd6eca547c8dad0 (diff) | |
| download | gdb-a9ff5f12cff6cd06f74ecf387ac5468984c94c6f.zip gdb-a9ff5f12cff6cd06f74ecf387ac5468984c94c6f.tar.gz gdb-a9ff5f12cff6cd06f74ecf387ac5468984c94c6f.tar.bz2 | |
Remove obsolete TYPE_FLAG_... values
Now that init_type no longer takes a FLAGS argument, there is no user of
the TYPE_FLAGS_... enum values left. This commit removes them (and all
references to them in comments as well).
This is mostly a no-op, except for a change to the Python type printer,
which attempted to use them before. (As best as I can tell, this wasn't
really needed anyway, since it was only used to pretty-print type
*instance* flags, which only use the instance flags.)
gdb/ChangeLog:
* gdbtypes.h (enum type_flag_value): Remove.
Remove references to TYPE_FLAG_... in comments throughout.
* gdbtypes.c (recursive_dump_type): Do not print TYPE_FLAG_...
flags, print the corresponding TYPE_... access macro names.
Remove references to TYPE_FLAG_... in comments throughout.
* infcall.c: Remove references to TYPE_FLAG_... in comments.
* valprint.c: Likewise.
* gdb-gdb.py (class TypeFlag): No longer consider TYPE_FLAG_...
values, only TYPE_INSTANCE_FLAG_... values.
(class TypeFlagsPrinter): Likewise.
gdb/testsuite/ChangeLog:
* gdb.cp/hang.exp: Remove reference to TYPE_FLAG_STUB in comment.
Signed-off-by: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Diffstat (limited to 'gdb/infcall.c')
| -rw-r--r-- | gdb/infcall.c | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/gdb/infcall.c b/gdb/infcall.c index 8199bdd..8595d9e 100644 --- a/gdb/infcall.c +++ b/gdb/infcall.c @@ -61,10 +61,9 @@ Unfortunately, on certain older platforms, the debug info doesn't indicate reliably how each function was defined. A function type's - TYPE_FLAG_PROTOTYPED flag may be clear, even if the function was - defined in prototype style. When calling a function whose - TYPE_FLAG_PROTOTYPED flag is clear, GDB consults this flag to - decide what to do. + TYPE_PROTOTYPED flag may be clear, even if the function was defined + in prototype style. When calling a function whose TYPE_PROTOTYPED + flag is clear, GDB consults this flag to decide what to do. For modern targets, it is proper to assume that, if the prototype flag is clear, that can be trusted: `float' arguments should be |