Displaying 4 results from an estimated 4 matches for "setinterruptfunct".
2011 Aug 21
4
[LLVMdev] Undefined references when LLVM is configured with "--host=x86_64-gnu-linux --target=x86_64-w64-mingw32"
...se/lib/libLLVMSupport.a(Signals.o):
In function `llvm::sys::RunInterruptHandlers()':
Signals.cpp:(.text+0x600): 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::SetInterruptFunction(void (*)())':
Signals.cpp:(.text+0x6c8): 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::RemoveFileOnSignal(llvm::sys::Path const&,
std::basic_string<...
2011 Aug 22
0
[LLVMdev] Undefined references when LLVM is configured with "--host=x86_64-gnu-linux --target=x86_64-w64-mingw32"
...ignals.o):
> In function `llvm::sys::RunInterruptHandlers()':
> Signals.cpp:(.text+0x600): 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::SetInterruptFunction(void (*)())':
> Signals.cpp:(.text+0x6c8): 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::RemoveFileOnSignal(llvm::sys::Path const&,...
2009 Feb 07
1
[LLVMdev] [PATCH] Use the new URL to BugPoint documentation
...educer. See\nhttp://"
- "llvm.org/docs/CommandGuide/bugpoint.html"
+ "llvm.org/cmds/bugpoint.html"
" for more information.\n");
sys::PrintStackTraceOnErrorSignal();
sys::SetInterruptFunction(BugpointInterruptFunction);
--
1.6.1.2.458.g9de76
2012 Jun 28
0
[LLVMdev] One problem to discuss
...SIGTYPE SignalHandler(int Sig) {
...
SignalsMutex.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 res...