Reid raised this issue in a bug comment that I thought should be discussed on the mailing list: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=540> I'm really not sure this is wise unless there is consensus that lli > should always be a multi-threaded program. Certainly, there's enough > problems with multi-threading that this could break many tests. I'd > like some other folks to chime in on this before we make this change.In order for LLVM to execute programs that are multithreaded, the JIT must be thread-safe. I am not aware of anyway of doing this "selectively." My patch (http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=418) adds a lock to ExecutionEngine.h, which means that the JIT must *always* be thread-safe, which means that it must always be linked against a platform's thread library. So the question is: Should the JIT always have locks, and always be thread-safe? This question really means "should LLVM always be capable of executing multithreaded programs?" Evan Jones -- Evan Jones http://evanjones.ca/
On May 13, 2005, at 20:30, Evan Jones wrote:> should LLVM always be capable of executing multithreaded programs?On a related note, I've updated my patch to fix the bug that I found in it, and I discussed on the mailing list last month. The details can be found in the bug: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=418 This is definitely *not* something that should go in before 1.5 is released, but I would love to see it integrated shortly after. Evan Jones -- Evan Jones http://evanjones.ca/
On Sat, 2005-05-14 at 13:10 -0400, Evan Jones wrote:> On May 13, 2005, at 20:30, Evan Jones wrote: > > should LLVM always be capable of executing multithreaded programs? > > On a related note, I've updated my patch to fix the bug that I found in > it, and I discussed on the mailing list last month. The details can be > found in the bug: > > http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=418Cool, thanks.> > This is definitely *not* something that should go in before 1.5 is > released, but I would love to see it integrated shortly after.Okay. Reid -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050514/620cab3a/attachment.sig>