public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51910] [4.7 Regression] -frepo linking failure
Date: Fri, 27 Jan 2012 21:02:00 -0000	[thread overview]
Message-ID: <bug-51910-4-YdWtGwj5Dl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51910-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-27 20:24:14 UTC ---
As can be seen from Jason's example, -frepo option is unfortunately not
mandatory on the link line when some objects have been compiled with -frepo.
And collect2 seems to work by running the linker, if it succeeded, fine,
otherwise look for *.rpo files around, try to parse the error output from the
linker, compile something again, link again.

So it would need to be done always.  Or perhaps tlink.c could somehow always
handle all the symbols that demangle the same together if the linker error
output contains demangled symbols.  Jason, do you think it would be possible?


  parent reply	other threads:[~2012-01-27 20:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20  2:59 [Bug c++/51910] New: " nephatrine at gmail dot com
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 [this message]
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-YdWtGwj5Dl@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).