On Mon, Sep 24, 2012 at 10:16:23PM +0200, Roland Scheidegger wrote:
> >> 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 versi
Am 24.09.2012 21:25, schrieb 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,
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 L
Alexander,
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_compi
From: "Alexander V. Nikolaev"
LLVM 3.1+ haven't more "extern unsigned llvm::StackAlignmentOverride"
and friends for configuring code generation options, like stack
alignment.
So I restrict assiging of lvm::StackAlignmentOverride and other
variables to LLVM 3.0 only, and wrote similiar code using
