New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to link all tools with thread libraries #912
Comments
I can help here, but I'm unsure what changes you're requesting. I don't think HOWEVER, I'm really not sure this is wise unless there is consensus that lli |
Well, to be more specific, anything that pulls in "ExecutionEngine.h" needs to link the thread library, Well, to be clear, it isn't that lli itself is multithreaded. My patch explicitly makes sure that the JIT This reminds me: I need to update my patch... |
We need some consensus on whether we link tools that use ExecutionEngine.h (e.g. Its fine with me. What say others? |
Personally I would like to defer that decision to the tool builder. For -Chris |
Here's what I've done to resolve this situation:
This means that, by default, all LLVM tools will link against libpthread if it For Win32, there are no alternate threading tools that make sense so we don't |
Extended Description
In order to support a multithreaded JIT, the LLVM build process must also pull in the pthreads library.
This means that there must be autoconf detection for pthreads and all that sort of thing. I struggled for
a couple hours just trying to get LLVM to be able to "AutoRegen.sh" on my Debian system, and I was
unable to get it working. In Reid's mailing list post, he made it sound like it wouldn't be challenging for
him to do it.
The text was updated successfully, but these errors were encountered: