diff options
author | Thomas Schwinge <thomas@codesourcery.com> | 2021-08-31 23:30:25 +0200 |
---|---|---|
committer | Thomas Schwinge <thomas@codesourcery.com> | 2021-11-09 14:40:12 +0100 |
commit | 088199e5d0fc0d54f48af0783a2630a773bbb387 (patch) | |
tree | dc4ae7a9887625877b63e213a72b9c55f035e54c | |
parent | 2fc9b4d7b0cbc88e9986486329abe899a07729de (diff) | |
download | gcc-088199e5d0fc0d54f48af0783a2630a773bbb387.zip gcc-088199e5d0fc0d54f48af0783a2630a773bbb387.tar.gz gcc-088199e5d0fc0d54f48af0783a2630a773bbb387.tar.bz2 |
Generalize 'gcc/input.h:struct location_hash'
This is currently only used here ('gcc/input.h:class string_concat_db'), but is
actually generally useful, so advertize it as such.
Per the rationale given, we may use 'BUILTINS_LOCATION' as spare value for
'Deleted', in addition to the existing use of 'UNKNOWN_LOCATION' as spare value
for 'Empty'.
gcc/
* input.h (location_hash): Use 'BUILTINS_LOCATION' as spare value
for 'Deleted'. Turn into a '#define'.
-rw-r--r-- | gcc/input.h | 24 |
1 files changed, 22 insertions, 2 deletions
diff --git a/gcc/input.h b/gcc/input.h index f7b08bd..bc44ba2 100644 --- a/gcc/input.h +++ b/gcc/input.h @@ -36,6 +36,28 @@ extern GTY(()) class line_maps *saved_line_table; both UNKNOWN_LOCATION and BUILTINS_LOCATION fit into that. */ STATIC_ASSERT (BUILTINS_LOCATION < RESERVED_LOCATION_COUNT); +/* Hasher for 'location_t' values satisfying '!RESERVED_LOCATION_P', thus able + to use 'UNKNOWN_LOCATION'/'BUILTINS_LOCATION' as spare values for + 'Empty'/'Deleted'. */ +/* Per PR103157 "'gengtype': 'typedef' causing infinite-recursion code to be + generated", don't use + typedef int_hash<location_t, UNKNOWN_LOCATION, BUILTINS_LOCATION> + location_hash; + here. + + It works for a single-use case, but when using a 'struct'-based variant + struct location_hash + : int_hash<location_t, UNKNOWN_LOCATION, BUILTINS_LOCATION> {}; + in more than one place, 'gengtype' generates duplicate functions (thus: + "error: redefinition of 'void gt_ggc_mx(location_hash&)'" etc.). + Attempting to mark that one up with GTY options, we run into a 'gengtype' + "parse error: expected '{', have '<'", which probably falls into category + "understanding of C++ is limited", as documented in 'gcc/doc/gty.texi'. + + Thus, use a plain ol' '#define': +*/ +#define location_hash int_hash<location_t, UNKNOWN_LOCATION, BUILTINS_LOCATION> + extern bool is_location_from_builtin_token (location_t); extern expanded_location expand_location (location_t); @@ -233,8 +255,6 @@ public: location_t * GTY ((atomic)) m_locs; }; -struct location_hash : int_hash <location_t, UNKNOWN_LOCATION> { }; - class GTY(()) string_concat_db { public: |