search for: dontremovefileonsign

Currently a power failure or other hard crash can cause lld leave a temporary file around. The same is true for other llvm tools. As an example, put a breakpoint in Writer.cpp:236 ("writeBuildId()") and restart the run a few times. You will get t.tmp43a735a t.tmp4deeabb t.tmp9bacdd3 t.tmpe4115c4 t.tmpeb01fff The same would happen if there was a fatal error between the

...ic_string<char, std::char_traits<char>, std::allocator<char> >*)': Signals.cpp:(.text+0x790): undefined reference to `llvm::sys::MutexImpl::acquire()' /home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/Release/lib/libLLVMSupport.a(Signals.o): In function `llvm::sys::DontRemoveFileOnSignal(llvm::sys::Path const&)': Signals.cpp:(.text+0xad0): undefined reference to `llvm::sys::MutexImpl::acquire()' /home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/Release/lib/libLLVMSupport.a(Threading.o):Threading.cpp:(.text+0xa8): more undefined references to `llvm::sys::MutexI...

...har_traits<char>, std::allocator<char> >> *)': > Signals.cpp:(.text+0x790): undefined reference to > `llvm::sys::MutexImpl::acquire()' > /home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/Release/lib/libLLVMSupport.a(Signals.o): > In function `llvm::sys::DontRemoveFileOnSignal(llvm::sys::Path > const&)': > Signals.cpp:(.text+0xad0): undefined reference to > `llvm::sys::MutexImpl::acquire()' > /home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/Release/lib/libLLVMSupport.a(Threading.o):Threading.cpp:(.text+0xa8): > more undefined referen...

...ignalsMutex.acquire(); RemoveFilesToRemove(); ... } We can also find following code snippet in the same file: void llvm::sys::RunInterruptHandlers() { SignalsMutex.acquire(); RemoveFilesToRemove(); SignalsMutex.release(); } Similarly, there are SetInterruptFunction, RemoveFileOnSignal, DontRemoveFileOnSignal I am afraid there is deadlock risk if llvm running in multithread mode, the case it is designed to safeguard. Suppose, say when some thread runs into RunInterruptHandlers and acquire the Mutex, then it is preemptied by scheduler, and before it is reselected by scheduler, one signal is dispatche...