On 06/19/2018 04:37 AM, Thomas Schwinge wrote:
Hi!
In case that you have not yet found it:
On Mon, 11 Jun 2018 12:19:23 -0600, Martin Sebor <mse...@gmail.com> wrote:
I've been noticing a number of failures in LTO (and some other)
tests in my x86_64-builds most of which don't appear in results
reported on gcc-testresults (all those on lines that start with
with the '!' below) and that I don't recall seeing before.
The LTO tests seem to fail with errors like the one below:
/usr/bin/ld: /tmp/ccIaufZk.lto.o: plugin needed to handle lto object
FAIL: g++.dg/lto/pr64043 cp_lto_pr64043_0.o-cp_lto_pr64043_0.o link,
-flto -std=c++11
That looks like <https://gcc.gnu.org/PR86004>.
Yes, that's it. Thanks! I've updated the bug to hopefull nudge
it closer to resolution since I continue to see these failures in
my builds on x86_64-linux running Fedora 25 (and they are making
it easier to miss other failures/regressions caused by my own
changes).
Honza, are there any other solutions besides those you mention
in comment 6 on the bug? My builds run on a shared machine that
I'm not sure can be easily upgraded. I could build my own Binutils
and use it instead but it seems that a more robust solution is for
the GCC test harness to detect and handle this gracefully (the same
way other missing dependencies are detected and prevented from
causing test failures).
Martin
