public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nephatrine at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51910] New: -frepo linking failure
Date: Fri, 20 Jan 2012 02:59:00 -0000	[thread overview]
Message-ID: <bug-51910-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51910
           Summary: -frepo linking failure
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: nephatrine@gmail.com


Created attachment 26388
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26388
Minimal Testcase

I'm having an issue with -frepo apparently not instantiating typeinfo/vtables
at least on x86_64 (have not tested on other archs). It is creating .rpo files,
but it cannot find the functions at the relinking stage.

I've attached a minimal testcase. The code compiles cleanly on GCC 4.6.2
without any errors, but 4.7 chokes on it. Here is the output of 'make' on my
system for the testcase.

g++ -frepo -o main.o -c main.cpp
g++ -frepo -o testcase main.o
collect: recompiling main.cpp
collect: relinking
collect2: error: '_ZN3FooIiED0Ev' was assigned to 'main.rpo', but was not
defined during recompilation, or vice versa
main.o:main.cpp:function Foo<int>::~Foo(): error: undefined reference to
'Foo<int>::~Foo()'
main.o:main.cpp:function Bar::~Bar(): error: undefined reference to
'Foo<int>::~Foo()'
main.o:main.cpp:function vtable for Foo<int>: error: undefined reference to
'Foo<int>::~Foo()'
main.o:main.cpp:function vtable for Foo<int>: error: undefined reference to
'Foo<int>::haggis()'
main.o:main.cpp:function typeinfo for Foo<int>: error: undefined reference to
'typeinfo name for Foo<int>'
collect2: error: ld returned 1 exit status
make: *** [testcase] Error 1


             reply	other threads:[~2012-01-20  2:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20  2:59 nephatrine at gmail dot com [this message]
2012-01-20  3:44 ` [Bug c++/51910] [4.7 Regression] " pinskia at gcc dot gnu.org
2012-01-20  4:05 ` nephatrine at gmail dot com
2012-01-20  4:06 ` pinskia at gcc dot gnu.org
2012-01-20  6:23 ` nephatrine at gmail dot com
2012-01-22 23:13 ` nephatrine at gmail dot com
2012-01-23 10:52 ` rguenth at gcc dot gnu.org
2012-01-23 22:42 ` jason at gcc dot gnu.org
2012-01-23 23:44 ` sandra at codesourcery dot com
2012-01-27 10:13 ` jakub at gcc dot gnu.org
2012-01-27 10:42 ` jakub at gcc dot gnu.org
2012-01-27 11:32 ` jakub at gcc dot gnu.org
2012-01-27 16:07 ` sandra at codesourcery dot com
2012-01-27 16:37 ` jakub at gcc dot gnu.org
2012-01-27 20:45 ` sandra at codesourcery dot com
2012-01-27 21:02 ` jakub at gcc dot gnu.org
2012-01-27 23:37 ` sandra at codesourcery dot com
2012-01-29 10:46 ` sandra at codesourcery dot com
2012-01-30  4:18 ` sandra at codesourcery dot com
2012-02-11  8:51 ` jason at gcc dot gnu.org
2012-02-11  9:17 ` jakub at gcc dot gnu.org
2012-02-17 19:04 ` sandra at codesourcery dot com

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-51910-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).