Hacker News Reader

I'm not sure what is meant here.

"opting in" to VS 2017 is recommended when building Chrome for 64-bit Windows to get improved incremental linking support. (We still link Chrome on Windows with link.exe even when compiling with Clang.)

View on HN

> (We still link Chrome on Windows with link.exe even when compiling with Clang.)

I wasn't aware of this, I know Rui the COFF owner in lld puts in a lot of effort into lld for chrome link times. Maybe he just uses it as a benchmark then :D

I actually caused a regression in migrating def code from lld to llvm with symbol mangling because we were missing a test case for this specific type of mangling and within hours it ended up on a chromium bug tracker and was fixed also within hours by Reid another googler on LLVM.

Yes, I should have been a bit more clear. You can link with lld (we have bots running that do this; we're even setting up a bot that enables ThinLTO). But lld support for emitting PDB files isn't quite there yet.

Not true anymore, I've updated the repository and article to work with 2017. Visual Studio 2017 doesn't require the -fms-compatibility flags anymore, in fact, it refuses to compile if you specify them. Since I was expecting these to be required I found no way to compile them.

Reply on news.ycombinator.com