News for hackers. Stuff that matters.
Re:Clang Is Now Used to Build Chrome for Windows by gsnedders on Monday March 05, 2018 @05:31PM (#16525166)
> edited to add: to be fair, it's not ABI compatible with MSVC. But it deserves a mention and it's an easier option than MSVC-style build systems for many open source projects.

Pretty sure this is significant in Chrome's case.

Re:Clang Is Now Used to Build Chrome for Windows by saurik on Tuesday March 06, 2018 @01:33AM (#16527276)
Why, though? What does Chrome do that calls into C++ code compiled by anyone but Google?
Re:Clang Is Now Used to Build Chrome for Windows by valarauca1 on Tuesday March 06, 2018 @03:11AM (#16527597)
on Windows the native ABI (or the default ABI I should say) explicitly reserves space for C++ stack unwinding on a per call basis.

A lot of the windows API can (ab)use this so it’s best to follow it, despite it being C (ish).

Re:Clang Is Now Used to Build Chrome for Windows by gsnedders on Tuesday March 06, 2018 @05:33AM (#16528025)
File dialogs (to save/load web pages, to upload files), print support, TCP sockets… all of these involve calling into system code.
Re:Clang Is Now Used to Build Chrome for Windows by tavert on Tuesday March 06, 2018 @10:05AM (#16529234)
do any of those require ABI compatibility at the C++ level? win32 API's are generally exposed as C
Re:Clang Is Now Used to Build Chrome for Windows by Const-me on Tuesday March 06, 2018 @11:45AM (#16529946)
> win32 API's are generally exposed as C

A lot of newer Win32 APIs are IUnknown-based COM interfaces. APIs that are probably relevant for Chrome are shell interop, drag & drop, Direct2D, Direct Write, Media Foundation.