[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #7 from patchapp at dberlin dot org 2007-04-16 15:00 --- Subject: Bug number PR 31144 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-04/msg00985.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
-- tobi at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |tobi at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2007-03-16 16:27:41 |2007-04-16 15:12:04 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #8 from tobi at gcc dot gnu dot org 2007-04-17 01:09 --- Subject: Bug 31144 Author: tobi Date: Tue Apr 17 01:09:34 2007 New Revision: 123904 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=123904 Log: PR fortran/31144 fortran/ * decl.c (gfc_sym_mangled_identifier): Use capital letters in name mangling. (gfc_sym_mangled_function_id): Likewise. testsuite/ * gfortran.dg/module_naming_1.f90: New. Added: trunk/gcc/testsuite/gfortran.dg/module_naming_1.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-decl.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #9 from tobi at gcc dot gnu dot org 2007-04-17 01:12 --- Fixed. -- tobi at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #4 from tobi at gcc dot gnu dot org 2007-03-21 12:13 --- (In reply to comment #3) FX' suggestion may fail if dots turn out to be non-portable. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2007-03-21 14:00 --- (In reply to comment #4) FX' suggestion may fail if dots turn out to be non-portable. The GNU as documentation says: Symbol names begin with a letter or with one of `._'. On most machines, you can also use $ in symbol names; exceptions are noted in Machine Dependencies. That character may be followed by any string of digits, letters, dollar signs (unless otherwise noted in Machine Dependencies), and underscores. So the strictest possible set of names: [a-zA-Z._][a-zA-Z0-9]* We should see if there are other requirements, e.g. when GCC is built with a system assembler that is not the GNU as. Otherwise, I think we'll have to go with uppercase. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added CC||fxcoudert at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #6 from tobi at gcc dot gnu dot org 2007-03-21 15:12 --- That should work, C++ mangles names to something like _ZN9wikipedia7article8wikilinkC1ERKSs NB your regexp is missing the underscore inside the second pair of brackets :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144
[Bug fortran/31144] gfortran module symbol names are not standard compliant
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2007-03-16 16:27 --- Confirmed, this should be fixed for 4.3.0 Intel and Portland compilers use a broken mechanism. Sun gives the following name to symbol FOO in module MOD: mod.foo_ It seems clean to me. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords||rejects-valid Known to fail||4.1.3 4.2.0 4.3.0 Last reconfirmed|-00-00 00:00:00 |2007-03-16 16:27:41 date|| Summary|Gfortran module names are |gfortran module symbol names |not Standards compliant |are not standard compliant Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31144