diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2020-04-23 14:43:18 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2020-04-23 14:43:18 +0200 |
| commit | 239cfd92e9ce5014a7616f692e0c6d4f337227b8 (patch) | |
| tree | 02e7f6592dba678e4eebd3259f72d1b225c69f53 /gcc/fortran/expr.c | |
| parent | c6ffc89f6ef90707ac44240718e258c81f32c7e4 (diff) | |
| download | gcc-239cfd92e9ce5014a7616f692e0c6d4f337227b8.zip gcc-239cfd92e9ce5014a7616f692e0c6d4f337227b8.tar.gz gcc-239cfd92e9ce5014a7616f692e0c6d4f337227b8.tar.bz2 | |
rs6000: Small improvement to the C++17 ABI fix [PR94707]
Anyway, based on IRC discussion with Richard Sandiford on IRC, we should
probably test type uids instead of type pointers because type uids aren't
reused, but type pointers in a very bad luck case could be, and having the
static var at filescope and GTY((deletable)) is an overkill (and with costs
during GC time).
2020-04-23 Jakub Jelinek <jakub@redhat.com>
PR target/94707
* config/rs6000/rs6000-call.c (rs6000_discover_homogeneous_aggregate):
Use TYPE_UID (TYPE_MAIN_VARIANT (type)) instead of type to check
if the same type has been diagnosed most recently already.
Diffstat (limited to 'gcc/fortran/expr.c')
0 files changed, 0 insertions, 0 deletions