https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95366
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Thomas Kथà¤nig <tkoe...@gcc.gnu.org>: https://gcc.gnu.org/g:858b288d2a6afc2f71f817344be3af4b7c3d4b3f commit r10-8427-g858b288d2a6afc2f71f817344be3af4b7c3d4b3f 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/95366 * 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. (cherry picked from commit 5958b926dcc3332aec0a2e34653c4394d2613401)
