Displaying 3 results from an estimated 3 matches for "146e560a".
Did you mean:
146560
2018 Jan 19
0
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
Hi,
No I didn't, I used cl.exe from the visual studio toolchain. What I'm
proposing is a tool for processing .obj files in COFF format, reading them
and generating the GHASH part.
To make our build faster we use hundreds of unity build files (.cpp's with
a lot of other .cpp's in them aka munch files) but still have a lot of
single .cpp's as well (in total something like 3.4k
2018 Jan 19
4
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
-lldb-dev, +llvm-dev
lldb-dev is specifically for the llvm debugger, and llvm-dev is for
everything else (including lld)
Did you compile the object files with clang and use -mllvm
-emit-codeview-ghash-section?
It sounds like probably not. If you don’t do that /DEBUG:GHASH will indeed
be much slower. I wonder if we should emit a linker diagnostic in this case
On Fri, Jan 19, 2018 at 12:09 PM
2018 Jan 19
4
[lldb-dev] Trying out lld to link windows binaries (using msvc as a compiler)
..., I can offer some guidance on where to look
in the code. Otherwise it's something that we'll probably get to, I'm just
not sure when.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180119/146e560a/attachment.html>