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
- Original Message -
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
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,
- Original Message -
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
On Thu, 2012-07-26 at 07:52 -0700, Jose Fonseca wrote:
- Original Message -
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
- Original Message -
On Thu, 2012-07-26 at 07:52 -0700, Jose Fonseca wrote:
- Original Message -
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
On Thu, 2012-07-26 at 10:31 -0700, Jose Fonseca wrote:
- Original Message -
On Thu, 2012-07-26 at 07:52 -0700, Jose Fonseca wrote:
- Original Message -
On 7/21/12 5:53 AM, Jose Fonseca wrote:
- Original Message -
Hi guys
LLVM 2.8 doesn't appear
- Original Message -
On Thu, 2012-07-26 at 10:31 -0700, Jose Fonseca wrote:
- Original Message -
On Thu, 2012-07-26 at 07:52 -0700, Jose Fonseca wrote:
- Original Message -
On 7/21/12 5:53 AM, Jose Fonseca wrote:
- Original Message -
Hi
On Thu, 2012-07-26 at 11:35 -0700, Jose Fonseca wrote:
- Original Message -
On Thu, 2012-07-26 at 10:31 -0700, Jose Fonseca wrote:
- Original Message -
On Thu, 2012-07-26 at 07:52 -0700, Jose Fonseca wrote:
- Original Message -
On 7/21/12 5:53 AM,
Hi guys
LLVM 2.8 doesn't appear to have mcjit, so we end up with no llvm libs
defined, look at the recent build failures in tinderbox.x.org.
Dave.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
- 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
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).
The attached patch should fix, but I don't have a machine with old llvm now.
Jose
- Original Message -
- 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
- Original Message -
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
I went ahead and pushed it. Hopefully it should fix it.
Jose
- Original Message -
The attached patch should fix, but I don't have a machine with old
llvm now.
Jose
- Original Message -
- Original Message -
Hi guys
LLVM 2.8 doesn't appear to have mcjit,
15 matches
Mail list logo
