Comment 15 for bug 1689294

Yes, that's going to be hard. The problem exists on my proprietary project I cannot publish from obvious reasons. It's big, it's several libraries + main code, I can't figure out which library triggers lto-wrapper.exe at the final stage. A variant with exceptions works on one build server, but fails on another with the same error.

Moreover, removing -flto from my main project, the one that links others (build with -flto) still calls for lto-wrapper.exe.

I tried to recreate problem in an example code, but so far no luck. The example build even with extra stuff in it. I'll be trying, because I need working solution with -flto for all.

I have not idea why adding locations of make.exe and the compiler into PATH doesn't solve the problem. I suspect there are some nested calls to gcc and/or something else. Is there any extra environment variable I should have set???

Can you answer this question:
- Is a bug fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89183 included in 8.3.1-2019q3?