<div dir="ltr">Why doesn't llvm::call_once() just use std::call_once on Windows?</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 8, 2017 at 12:40 PM Hans Wennborg <<a href="mailto:hans@chromium.org">hans@chromium.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The Win64 lldb build seems broken (at 294367).<br class="gmail_msg">
<br class="gmail_msg">
I ran into this when trying to build the weekly snapshot<br class="gmail_msg">
(<a href="http://www.llvm.org/builds/" rel="noreferrer" class="gmail_msg" target="_blank">http://www.llvm.org/builds/</a>) which includes LLDB these days.<br class="gmail_msg">
<br class="gmail_msg">
I suspect this might be related to Kamil's changes a few days ago. I<br class="gmail_msg">
see Pavel committed something to fix Darwin afterwards.<br class="gmail_msg">
<br class="gmail_msg">
Zach, do you know what's going on here? Do we have any buildbot<br class="gmail_msg">
coverage for this?<br class="gmail_msg">
<br class="gmail_msg">
   Creating library lib\liblldb.lib and object lib\liblldb.exp<br class="gmail_msg">
lldbHost.lib(HostInfoWindows.cpp.obj) : error LNK2019: unresolved external symbo<br class="gmail_msg">
l "void __cdecl llvm::sys::_mm_mfence(void)" (?_mm_mfence@sys@llvm@@YAXXZ) refer<br class="gmail_msg">
enced in function "void __cdecl llvm::call_once<class <lambda_e212a11f7f891e804e<br class="gmail_msg">
713e15728a6adc> >(struct llvm::once_flag &,class <lambda_e212a11f7f891e804e713e1<br class="gmail_msg">
5728a6adc> &&)" (??$call_once@V<lambda_e212a11f7f891e804e713e15728a6adc>@@$$V@ll<br class="gmail_msg">
vm@@YAXAEAUonce_flag@0@$$QEAV<lambda_e212a11f7f891e804e713e15728a6adc>@@@Z)<br class="gmail_msg">
bin\liblldb.dll : fatal error LNK1120: 1 unresolved externals<br class="gmail_msg">
LINK failed. with 1120<br class="gmail_msg">
</blockquote></div>