On 7/21/12 5:53 AM, Jose Fonseca wrote:
----- Original Message -----
Hi guys
LLVM 2.8 doesn't appear to have mcjit, so we end up with no llvm libs
defined,
Yes, mcjit is only used/necessary from llvm-3.1 onwards, so the autoconf code
should check conditiionally.
BTW, I'll soon commit a change that will stop using mcjit from 3.2 onwards (as
with the current LLVM 3.2 trunk, AVX is supported by the old jit, which is more
stable/polished).
Is there a long-term plan or theory for which jit we'll be using? Are
we just following upstream? Are the problems of mcjit simply a superset
of the problems with the old jit?
I know there are people interested in supporting other arches in
llvmpipe, so it'd be nice if they knew what to work on. And personally
the gdb integration bit of mcjit sounds really appealing from a support
perspective.
- ajax
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
