public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "t at sharklasers dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/66029] Build error compiling gcc5.1 using LTO
Date: Thu, 07 May 2015 23:58:00 -0000	[thread overview]
Message-ID: <bug-66029-4-PcFSwwIhki@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66029-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66029

--- Comment #11 from JD <t at sharklasers dot com> ---
Yes, it's non-empty:

$ ar --help | grep plugin
Usage: ar [emulation options] [-]{dmpqrstx}[abcDfilMNoPsSTuvV] [--plugin
<name>] [member-name] [count] archive-file file...
  --plugin <p> - load the specified plugin
ar: supported targets: elf64-x86-64 elf32-i386 elf32-x86-64 a.out-i386-linux
pei-i386 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big elf32-little
elf32-big plugin srec symbolsrec verilog tekhex binary ihex


$  echo "int main () {}" | gcc -x c++ -O2 - -flto -v 2>&1 | grep "collect2
-plugin"
 gcc5.1/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/collect2 -plugin
gcc5.1/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/liblto_plugin.so
-plugin-opt=gcc5.1/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper
-plugin-opt=-fresolution=/tmp/ccuU0Nuu.res -plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -flto
--eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2
/usr/lib/../lib64/crt1.o /usr/lib/../lib64/crti.o
gcc5.1/lib64/gcc/x86_64-unknown-linux-gnu/5.1.0/crtbegin.o
-Lgcc5.1/lib64/gcc/x86_64-unknown-linux-gnu/5.1.0
-Lgcc5.1/lib64/gcc/x86_64-unknown-linux-gnu/5.1.0/../../../../lib64
-L/lib/../lib64 -L/usr/lib/../lib64
-Lgcc5.1/lib64/gcc/x86_64-unknown-linux-gnu/5.1.0/../../.. /tmp/ccUoazVJ.o
-lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s
--no-as-needed gcc5.1/lib64/gcc/x86_64-unknown-linux-gnu/5.1.0/crtend.o
/usr/lib/../lib64/crtn.o


      parent reply	other threads:[~2015-05-07 23:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 22:21 [Bug lto/66029] New: " t at sharklasers dot com
2015-05-05 22:25 ` [Bug lto/66029] " t at sharklasers dot com
2015-05-05 23:24 ` hjl.tools at gmail dot com
2015-05-05 23:30 ` pinskia at gcc dot gnu.org
2015-05-06 14:15 ` t at sharklasers dot com
2015-05-06 14:17 ` t at sharklasers dot com
2015-05-06 14:21 ` trippels at gcc dot gnu.org
2015-05-06 14:48 ` hjl.tools at gmail dot com
2015-05-07 15:15 ` trippels at gcc dot gnu.org
2015-05-07 23:58 ` t at sharklasers dot com [this message]

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-66029-4-PcFSwwIhki@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).