On 7/26/12 10:52 AM, Jose Fonseca wrote:
----- Original Message -----
Are the problems of mcjit simply a superset
of the problems with the old jit?
The only reason we started to look at mcjit was because old jit didn't support
avx. But on current trunk (ie llvm-3.2) it does.
To be honest, apart of avx, none of the benefits of mcjit matter to me:
- we're not compiling from a C source file (or any kind of source file), so not
sure what GDB integration will bring
and all its shortcomings affect me
I don't think this is essentially true, just temporally true. Imagine a
consumer more like OpenCL than OpenGL. Or, imagine being able to
breakpoint and single-step in your GL shaders to see where something
complicated goes wrong.
IMO, mcjit it's not production quality, and progress has been awfully slow.
That sounds decisive enough for me, thanks.
- ajax
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
