public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/55636] New: [4.8 Regression] Fortran name mangling collides with user namespace
@ 2012-12-10  0:39 dje at gcc dot gnu.org
  2012-12-10  0:43 ` [Bug fortran/55636] " dje at gcc dot gnu.org
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: dje at gcc dot gnu.org @ 2012-12-10  0:39 UTC (permalink / raw)
  To: gcc-bugs


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55636

             Bug #: 55636
           Summary: [4.8 Regression] Fortran name mangling collides with
                    user namespace
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dje@gcc.gnu.org


As reported in early October, a patch added name mangling to some additional
symbols. The mangling is wrong for a number of reasons:

1) It conflicts with naming used in some systems (AIX)
2) It does not obey NO_DOT_IN_LABEL
3) It does not use identifiers reserved to the system

A proposal to use "_F" prefix instead of "." was proposed and discussed, but
there has been no progress.


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2012-12-19  9:28 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-10  0:39 [Bug fortran/55636] New: [4.8 Regression] Fortran name mangling collides with user namespace dje at gcc dot gnu.org
2012-12-10  0:43 ` [Bug fortran/55636] " dje at gcc dot gnu.org
2012-12-10  8:13 ` burnus at gcc dot gnu.org
2012-12-10  8:38 ` rguenth at gcc dot gnu.org
2012-12-10  8:51 ` janus at gcc dot gnu.org
2012-12-10  9:39 ` jakub at gcc dot gnu.org
2012-12-11 11:22 ` janus at gcc dot gnu.org
2012-12-19  9:21 ` burnus at gcc dot gnu.org
2012-12-19  9:28 ` burnus at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).