Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

Rename location accessor macro parameters to silence ARI

Browse Source 
The locations patch I recently committed contains macro definitions
such as:

This causes an ARI error to be emitted by the server ("Do not use PTR, ISO C
90 implies `void *'").  While this ARI error is bogus in this context,
it is just easiest to squash the error completely by renaming the macro
parameters.

gdb/ChangeLog

	* location.c (EL_TYPE, EL_LINESPEC, EL_PROBE, EL_ADDRESS)
	(EL_EXPLICIT, EL_STRING): Change macro parameter to "P" to
	silence ARI errors.
This commit is contained in:
Keith Seitz
2015-08-14 15:00:04 -07:00
parent 9ca98f9278
commit ebdad8fc7f
2 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
gdb/location.c
View File

@@ -36,7 +36,7 @@ struct event_location
{
/* The type of this breakpoint specification. */
enum event_location_type type;
#define EL_TYPE(PTR) (PTR)->type
#define EL_TYPE(P) (P)->type
union
{
@@ -44,22 +44,22 @@ struct event_location
This representation is used by both "normal" linespecs and
probes. */
char *addr_string;
#define EL_LINESPEC(PTR) ((PTR)->u.addr_string)
#define EL_PROBE(PTR) ((PTR)->u.addr_string)
#define EL_LINESPEC(P) ((P)->u.addr_string)
#define EL_PROBE(P) ((P)->u.addr_string)
/* An address in the inferior. */
CORE_ADDR address;
#define EL_ADDRESS(PTR) (PTR)->u.address
#define EL_ADDRESS(P) (P)->u.address
/* An explicit location. */
struct explicit_location explicit_loc;
#define EL_EXPLICIT(PTR) (&((PTR)->u.explicit_loc))
#define EL_EXPLICIT(P) (&((P)->u.explicit_loc))
} u;
/* Cached string representation of this location. This is used, e.g., to
save stop event locations to file. Malloc'd. */
char *as_string;
#define EL_STRING(PTR) ((PTR)->as_string)
#define EL_STRING(P) ((P)->as_string)
};
/* See description in location.h. */