Open kayhayen opened 2 years ago
Do you have the same problem without ccache?
Yes it does, but good point, didn't think of that.
I never got ccache 4 to work properly on Windows. Version 3 worked better, but I usually build without until they get it working properly....
But ccache is not part of the equation, it doesn't work without it either.
I think it's really that some LTO support is missing from the clang linker, much like it did for gcc some time ago. The linking side seems to not support the bytecode written by the compiler backend. I assume there is a missing bit somewhere. For what it's worth, I believe that Clang based on MSVC works for LTO, but I need to verify if it's really doing it.
Hello,
with Nuitka I have LTO working with MinGW64. However, when I enable it with Clang, at link time, it tells me it doesn't understand the file format of the
.o
files. Looking at it withfile
it tells me it is bytecode.But first without, this command line from the command:
gives me:
And that works, and has been used every since Clang on MinGW64 was made to work with Nuitka. Currently it's regressed a bit, so factory branch would have to be used, to not have to say
--lto=no
.However, with yes, I get this:
However, it gets rejected as
file not recognized: file format not recognized
and that's at link time using this command:Right now I am assuming that LTO with Clang as distributed by winlibs is just not supported. However, I feel that makes comparing performance between GCC and Clang a bit unfair here.
Yours, Kay