[Mesa-dev] [PATCH 1/1] gallium/gallivm: code generation options for LLVM 3.1+

[Alexander V. Nikolaev]

On Mon, Sep 24, 2012 at 07:20:31AM -0700, Jose Fonseca wrote:

> Thanks for nailing this. There are still several outstanding bug 
> reports for WINE and LLVM and I never managed to make much progress.
> 
> This only covers the MCJIT case, but for LLVM 3.2 we no longer use 
> MCJIT, and just call LLVMCreateJITCompiler (instead of
> lp_build_create_mcjit_compiler_for_module). So I think we need to 
> create another version of 
> lp_build_create_mcjit_compiler_for_module/LLVMCreateJITCompiler that 
> sets up the target as we need it.
> 

EngineBuilder in lp_build_create_mcjit_compiler_for_module 
has option builder.setUseMCJIT(true); I think this behavior should be 
configurable via GALLIVM_DEBUG or even via own variable.
Or you plan to eliminate ExecutionEngine using at all?
(btw -- what minimal LLVM version supported by gallium? maybe some 
ifdef's are deprecated?)

Could I try to help with improvement of LLVM related stuff?
(May be if someone gives me few hints).

Also I want to help with finishing autotooling src/gallium/ (just 
because out-of-source building will be less painful, if we need to 
build same source against many versions of LLVM)