[Mesa-dev] [PATCH 0/3] Softpipe draw de-LLVM-fication.

[Brian Paul]

On 01/09/2012 01:32 PM, Jakob Bornecrantz wrote:
> On Mon, Jan 9, 2012 at 9:27 PM, Brian Paul<brianp at vmware.com>  wrote:
>> On 01/09/2012 12:51 PM, Jakob Bornecrantz wrote:
>>>
>>> On Mon, Jan 9, 2012 at 8:35 PM, Brian Paul<brianp at vmware.com>    wrote:
>>>>
>>>> On 01/09/2012 11:28 AM, Jakob Bornecrantz wrote:
>>>>>
>>>>>
>>>>> So it turns out that softpipe uses LLVM in the draw module
>>>>> since it has no way of telling draw not to use it. This patch
>>>>> series fixes that. Also makes the draw initialization fail
>>>>> if draw can't initialize LLVM in the normal case.
>>>>>
>>>>> Cheers, Jakob.
>>>>>
>>>>> Jakob Bornecrantz (3):
>>>>>    draw: Make it possible to create a llvm free context
>>>>>    draw: Fail if we fail to enable llvm when asked for it
>>>>>    softpipe: Don't use llvm in draw
>>>>>
>>>>>   src/gallium/auxiliary/draw/draw_context.c |   64
>>>>> ++++++++++++++++++++---------
>>>>>   src/gallium/auxiliary/draw/draw_context.h |    2 +
>>>>>   src/gallium/drivers/softpipe/sp_context.c |    2 +-
>>>>>   3 files changed, 47 insertions(+), 21 deletions(-)
>>>>>
>>>>
>>>> I guess I'd like a way to keep using LLVM with softpipe in some
>>>> circumstances (with a config/env var option).  I sometimes debug things
>>>> using softpipe and losing LLVM vertex processing would be a slow-down in
>>>> some cases.
>>>
>>>
>>> Would SOFTPIPE_FORCE_LLVM/SOFTPIPE_LLVM_VS work?
>>
>>
>> How about SOFTPIPE_USE_LLVM?
>
> Sounds good, updated patch sent.

Thanks.

For the series:
Reviewed-by: Brian Paul <brianp at vmware.com>

BTW, you might want to document this var in docs/envvars.html

-Brian