public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d dot g dot gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/42690] Undefined reference errors with -flto -fuse-linker-plugin
Date: Sat, 16 Jan 2010 16:56:00 -0000	[thread overview]
Message-ID: <20100116165550.13892.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42690-16926@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from d dot g dot gorbachev at gmail dot com  2010-01-16 16:55 -------
(In reply to comment #12)

> What options other than -nostdlib prevent gcc from linking libgcc and
> libc in the produced binary?

I know of -nodefaultlibs.

> To implement this we should always pass -plugin-opt=-pass-through=
> %(lto_libgcc) and -plugin-opt=-pass-through=-lc to the linker unless
> something like -nostdlib is used.

Wouldn't it be better to add %{fuse-linker-plugin:
-plugin-opt=-pass-through=...} to LIBGCC_SPEC and to LIB_SPEC?

However, the driver does not really know, whether we link with libgcc and/or
libc. Someone can use -nodefaultlibs together with -lc -lgcc and the linker
will still fail.


-- 


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


  parent reply	other threads:[~2010-01-16 16:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 15:23 [Bug lto/42690] New: " d dot g dot gorbachev at gmail dot com
2010-01-11 15:25 ` [Bug lto/42690] " d dot g dot gorbachev at gmail dot com
2010-01-12 16:30 ` espindola at gcc dot gnu dot org
2010-01-14 22:15 ` d dot g dot gorbachev at gmail dot com
2010-01-15  3:41 ` hjl dot tools at gmail dot com
2010-01-15  3:55 ` espindola at gcc dot gnu dot org
2010-01-15  4:26 ` hjl dot tools at gmail dot com
2010-01-15 11:02 ` d dot g dot gorbachev at gmail dot com
2010-01-15 11:02 ` d dot g dot gorbachev at gmail dot com
2010-01-15 11:02 ` d dot g dot gorbachev at gmail dot com
2010-01-15 11:03 ` d dot g dot gorbachev at gmail dot com
2010-01-15 11:04 ` [Bug driver/42690] " d dot g dot gorbachev at gmail dot com
2010-01-15 15:29 ` espindola at gcc dot gnu dot org
2010-01-16 16:56 ` d dot g dot gorbachev at gmail dot com [this message]
2010-01-17  5:47 ` espindola at gcc dot gnu dot org
2010-01-18 18:48 ` d dot g dot gorbachev at gmail dot com
     [not found] <bug-42690-4@http.gcc.gnu.org/bugzilla/>
2010-11-10  3:59 ` davek at gcc dot gnu.org
2010-11-16 15:05 ` davek at gcc dot gnu.org
2010-11-16 16:33 ` davek at gcc dot gnu.org
2010-11-20 20:53 ` hjl.tools at gmail dot com
2010-11-20 21:04 ` davek at gcc dot gnu.org
2010-11-20 21:07 ` hubicka at gcc dot gnu.org
2010-11-20 21:14 ` hubicka at gcc dot gnu.org
2010-11-20 21:50 ` hjl.tools at gmail dot com
2010-11-22 18:03 ` hjl.tools at gmail dot com
2010-11-22 18:31 ` hjl.tools at gmail dot com
2010-11-23 19:20 ` davek at gcc dot gnu.org
2010-11-23 19:26 ` davek at gcc dot gnu.org
2010-11-23 23:53 ` hjl.tools at gmail dot com
2010-11-24 15:14 ` hjl.tools at gmail dot com
2010-11-25 11:14 ` rguenth at gcc dot gnu.org
2010-12-02 17:16 ` hjl.tools at gmail dot com
2010-12-04 17:37 ` hjl.tools at gmail dot com
2010-12-04 22:30 ` d.g.gorbachev at gmail dot com
2010-12-04 22:31 ` d.g.gorbachev at gmail dot com
2010-12-05  0:44 ` hjl.tools at gmail dot com
2010-12-05 12:37 ` d.g.gorbachev at gmail dot com
2010-12-05 16:49 ` d.g.gorbachev at gmail dot com
2010-12-05 18:24 ` hjl.tools at gmail dot com
2010-12-06 17:54 ` davek 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=20100116165550.13892.qmail@sourceware.org \
    --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).