https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95355
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Kथà¤nig <tkoe...@gcc.gnu.org>:
https://gcc.gnu.org/g:5958b926dcc3332aec0a2e34653c4394d2613401
commit r11-1729-g5958b926dcc3332aec0a2e34653c4394d2613401
Author: Thomas Koenig <tkoe...@gcc.gnu.org>
Date: Tue Jun 30 13:01:36 2020 +0200
Use CHARACTER(kind) string for calculating the type hash.
This regression came about because of a change in the way
types are displayed in error messages. The character
representation is also used to calculate the hashes for
our types, so this patch restores the old behavior if
we are indeed calculating a hash.
The test case also checks for the specific hash value because
changing that would be an ABI change, which we should not
be doing unintentionally.
gcc/fortran/ChangeLog:
2020-06-30 Thomas Koenig <tkoe...@gcc.gnu.org>
PR fortran/95355
* gfortran.h (gfc_typename): Add optional argument for_hash.
* misc.c (gfc_typename): When for_hash is true, just retur
CHARACTER(kind).
* class.c (gfc_intrinsic_hash_value): Call gfc_typename with
for_hash = true.
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #6)
> The master branch has been updated by Thomas Kथà¤nig <tkoe...@gcc.gnu.org>:
That last commit was for PR 95366.
