public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45053] libgcc_s link command misses crtsavgpr_s and crtresgpr_s for powerpc
Date: Thu, 07 Feb 2013 08:37:00 -0000	[thread overview]
Message-ID: <bug-45053-4-k63yqQ1QFO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45053-4@http.gcc.gnu.org/bugzilla/>


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

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |amodra at gmail dot com
         AssignedTo|unassigned at gcc dot       |amodra at gmail dot com
                   |gnu.org                     |

--- Comment #12 from Alan Modra <amodra at gmail dot com> 2013-02-07 08:36:45 UTC ---
Some of the claims made in various comments are wrong, at least for current
gcc-4.7 svn rev 195829.  Even the subject is wrong.  libgcc_s.so *is* linked
with the crtsav/res objects.  They are contained in libgcc.a, and libgcc.a is
used when linking libgcc_s.so.  I have verified that libgcc_s.so built with -Os
due to --enable-target-optspace does need various _savegpr* and _restgpr*
functions.

Comment #4 shows the real problem nicely.  Notice that the reference to
_savegpr_31 comes from crtend.o which the penultimate object on the linker
command line, *after* libgcc.a.  So if no other object linked needs the
out-of-line register save functions they won't be extracted from libgcc.a.

$ nm crtbegin.o | grep gpr
         U _restgpr_29_x
$ nm crtend.o | grep gpr
         U _restgpr_31_x
         U _savegpr_31


  parent reply	other threads:[~2013-02-07  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45053-4@http.gcc.gnu.org/bugzilla/>
2011-03-25 10:46 ` [Bug bootstrap/45053] " rguenth at gcc dot gnu.org
2012-04-12 14:44 ` [Bug target/45053] " rhabarber1848 at web dot de
2012-04-13 22:37 ` rhabarber1848 at web dot de
2013-02-07  8:37 ` amodra at gmail dot com [this message]
2013-02-07  8:41 ` amodra at gmail 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-45053-4-k63yqQ1QFO@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).