[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-03-20 Thread rguenth at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Richard Guenther changed: What|Removed |Added CC||rguenth at gcc dot gnu.org

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-03-20 Thread nheghathivhistha at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 David Kredba changed: What|Removed |Added CC||nheghathivhistha at gmail dot com --

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-04-03 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Bug 13227 depends on bug 14698, which changed state. Bug 14698 Summary: ar, nm and ranlib don't use gcc's liblto_plugin.so in BINDIR/../lib/bfd-plugins automatically https://sourceware.org/bugzilla/show_bug.cgi?id=14698 What|Re

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-04-03 Thread hubicka at ucw dot cz
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #2 from hubicka at ucw dot cz --- > Bug 14698 Summary: ar, nm and ranlib don't use gcc's liblto_plugin.so in > BINDIR/../lib/bfd-plugins automatically > https://sourceware.org/bugzilla/show_bug.cgi?id=14698 Will we now get some so

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-04-04 Thread rguenther at suse dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #3 from rguenther at suse dot de --- On Thu, 3 Apr 2014, hubicka at ucw dot cz wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=13227 > > --- Comment #2 from hubicka at ucw dot cz --- > > Bug 14698 Summary: ar, nm and ranl

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-27 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #4 from Alan Modra --- *** Bug 15300 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailin

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-27 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Alan Modra changed: What|Removed |Added CC||amodra at gmail dot com --- Comment #5 f

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-28 Thread rguenth at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #6 from Richard Guenther --- (In reply to Alan Modra from comment #5) > So is it sufficient (and safe) to warn just on the presence of > __gnu_slim_lto? Yes, I think so. -- You are receiving this mail because: You are on the CC

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-28 Thread hubicka at ucw dot cz
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #7 from hubicka at ucw dot cz --- > So is it sufficient (and safe) to warn just on the presence of __gnu_slim_lto? Yes, when __gnu_slim_lto gets into linking/archiving/nm, I think it is safe to warn about missing plugin. Honza --

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-28 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Alan Modra changed: What|Removed |Added Status|NEW |ASSIGNED CC|amodra at gm

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-28 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #8 from cvs-commit at gcc dot gnu.org --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch,

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-28 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Alan Modra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-29 Thread hubicka at ucw dot cz
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #10 from hubicka at ucw dot cz --- > Fixed Thanks, does this also cover gold linker? Honza -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-29 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #11 from Alan Modra --- No, I didn't do anything about gold. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-07-29 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #12 from Alan Modra --- Created attachment 7730 --> https://sourceware.org/bugzilla/attachment.cgi?id=7730&action=edit gold patch This should fix gold -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-08-05 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 --- Comment #13 from cvs-commit at gcc dot gnu.org --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch

[Bug binutils/13227] GCC now produce slim LTO files. Those can't be linked/archived or nm w/o plugin used. It would be useful to output diagnostics when user attempts so

2014-09-22 Thread gingold at adacore dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=13227 Bug 13227 depends on bug 14698, which changed state. Bug 14698 Summary: ar, nm and ranlib don't use gcc's liblto_plugin.so in BINDIR/../lib/bfd-plugins automatically https://sourceware.org/bugzilla/show_bug.cgi?id=14698 What|Re