public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46448] New: [4.6 Regression] [OOP] symbol `__copy_...' is already defined
Date: Fri, 12 Nov 2010 09:28:00 -0000	[thread overview]
Message-ID: <bug-46448-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.6 Regression] [OOP] symbol `__copy_...' is already
                    defined
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: janus@gcc.gnu.org


Simple test case:


module m0
  type :: t
  end type
end module 

module m1
  use m0
  class(t), pointer :: c1
end module

module m2
  use m0
  class(t), pointer :: c2
end module

end


This currently fails with:

/tmp/cciKD2sS.s: Assembler messages:
/tmp/cciKD2sS.s:72: Error: symbol `__copy_m0_t_' is already defined


The test case works with 4.5. The error is a regression of my recent
"polymorphic deep copy" patch:

http://gcc.gnu.org/viewcvs?view=revision&revision=166368


I think this is the same issue as the one reported by Salvatore here:

http://gcc.gnu.org/ml/fortran/2010-11/msg00205.html


             reply	other threads:[~2010-11-12  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  9:28 janus at gcc dot gnu.org [this message]
2010-11-12 10:10 ` [Bug fortran/46448] " sfilippone at uniroma2 dot it
2010-11-12 12:55 ` burnus at gcc dot gnu.org
2010-11-15 13:22 ` rguenth at gcc dot gnu.org
2010-12-31 22:52 ` sfilippone at uniroma2 dot it
2011-01-03 12:12 ` janus at gcc dot gnu.org
2011-01-04 12:59 ` janus at gcc dot gnu.org
2011-01-04 13:06 ` janus at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-46448-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).