This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, Fortran, OOP] PR 46971: [4.6 Regression] ICE on long class names
- From: Daniel Franke <franke dot daniel at gmail dot com>
- To: fortran at gcc dot gnu dot org
- Cc: Janus Weil <janus at gcc dot gnu dot org>, "gcc-patches" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 30 Dec 2010 18:24:06 +0100
- Subject: Re: [Patch, Fortran, OOP] PR 46971: [4.6 Regression] ICE on long class names
- References: <AANLkTikR1ZXi9Hz2DHYAOtsjAZt62n-2Cyu=mMQmFjRg@mail.gmail.com>
On Thursday 30 December 2010 18:05:15 Janus Weil wrote:
> So we just use this hash value (in hex representation) for the class
> container naming, e.g. "__class_12083EB", which guarantees to respect
> the 63 character limit. These names are not user-visible, of course,
> so this obfuscation's only negative effect may be in debugging the
> internal class symbols. Therefore we keep the name constructed from
> the old scheme if it is short enough, and only use the hash for those
> cases where the 63 character limit is violated.
Hi Janus,
why not use the hash names everywhere and have a field "realname" next to the
hash that holds the name, regardless of length?
Cheers
Daniel