public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gmarkhor at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/48947] 4.6.0 fails to link ffmpeg with LTO and gold Date: Wed, 11 May 2011 17:53:00 -0000 [thread overview] Message-ID: <bug-48947-4-glhcpFFLNj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48947-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48947 --- Comment #4 from Vadim Markovtsev <gmarkhor at gmail dot com> 2011-05-11 17:29:32 UTC --- I checked those errors with both binutils 2.21 release and 2.22 CVS (10th of May). gcc -### Using built-in specs. COLLECT_GCC=/???/x86_64-gcc-4.6.0/bin/gcc COLLECT_LTO_WRAPPER=/???/x86_64-gcc-4.6.0/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../configure --prefix=/???/x86_64-gcc-4.6.0 --enable-shared --with-arch=native --enable-languages=c,c++ --enable-lto --enable-plugin --enable-gold --enable-linker-build-id --disable-multilib --enable-ld=default --with-plugin-ld=ld.gold Thread model: posix gcc version 4.6.0 (GCC) If you mean CC=gcc -flto -fuse-linker-plugin, I get the same errors.
next prev parent reply other threads:[~2011-05-11 17:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-10 11:28 [Bug lto/48947] New: " gmarkhor at gmail dot com 2011-05-10 12:29 ` [Bug lto/48947] " rguenth at gcc dot gnu.org 2011-05-11 12:13 ` gmarkhor at gmail dot com 2011-05-11 12:27 ` rguenth at gcc dot gnu.org 2011-05-11 17:53 ` gmarkhor at gmail dot com [this message] 2011-05-12 9:28 ` rguenth at gcc dot gnu.org 2011-05-12 19:56 ` ian at airs dot com 2011-05-24 12:01 ` gmarkhor at gmail dot com 2011-05-24 12:02 ` gmarkhor at gmail dot com 2011-05-24 12:12 ` gmarkhor at gmail dot com 2012-07-14 20:45 ` leif.walsh at gmail dot com 2014-09-06 10:29 ` trippels 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=bug-48947-4-glhcpFFLNj@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).