public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "moonshine at kapsi dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/44802] -flto -fuse-linker-plugin causes undefined references from libc in the link phase Date: Sat, 03 Jul 2010 13:35:00 -0000 [thread overview] Message-ID: <20100703133515.1898.qmail@sourceware.org> (raw) In-Reply-To: <bug-44802-19380@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from moonshine at kapsi dot fi 2010-07-03 13:35 ------- On trunk the same link command fails too, but in a different way. I was able to produce a reduced testcase and filed a new report as these issues are probably not related. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44804 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44802
next prev parent reply other threads:[~2010-07-03 13:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-03 12:31 [Bug lto/44802] New: " moonshine at kapsi dot fi 2010-07-03 12:32 ` [Bug lto/44802] " moonshine at kapsi dot fi 2010-07-03 12:33 ` moonshine at kapsi dot fi 2010-07-03 13:35 ` moonshine at kapsi dot fi [this message] 2010-07-08 2:03 ` moonshine at kapsi dot fi 2010-07-26 21:14 ` hubicka at gcc dot gnu dot org 2010-07-27 12:42 ` moonshine at kapsi dot fi
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=20100703133515.1898.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: 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).