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/53803] --enable-target-optspace gives undefined references to restgpr_*_x Date: Fri, 29 Jun 2012 16:00:00 -0000 [thread overview] Message-ID: <bug-53803-4-FTedZXjLNB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53803-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53803 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #1 from Alan Modra <amodra at gmail dot com> 2012-06-29 15:58:57 UTC --- In reply to question (1), if you get "hidden symbol _restgpr_31_x ... is referenced by DSO" then the DSO (libc?) in question has been wrongly built. You can not have dynamic save/restore functions, so each shared library or executable must use local copies of those functions. In reply to observation (2) and (3), linking with -nostdlib means that you need to really know what you're doing. In this case you must link in some object or static library that provides the save/restore functions if you use them (as in -Os code), and, yes, linking against libgcc.a should do the trick. In reply to question (2), it sounds like you need to write some more code, or link against libgcc.a In reply to question (3), the restgpr_*_x calls are a variant of the gpr restore functions that tear down the stack frame and return, in addition to restoring registers.
next prev parent reply other threads:[~2012-06-29 16:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-29 10:20 [Bug target/53803] New: " aldot at gcc dot gnu.org 2012-06-29 16:00 ` amodra at gmail dot com [this message] 2012-06-29 16:04 ` [Bug target/53803] " 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-53803-4-FTedZXjLNB@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: linkBe 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).