mesa-8.0.5: LLVM-3.2 patchset and request for cherry-picking

Sedat Dilek sedat.dilek at gmail.com
Thu Jan 17 15:53:32 PST 2013


On Fri, Jan 18, 2013 at 12:44 AM, Brian Paul <brianp at vmware.com> wrote:
> On 01/17/2013 04:23 PM, Sedat Dilek wrote:
>>
>> Hi,
>>
>> with the following patchset (13 patches) I was able to build
>> mesa-8.0.5 with LLVM v3.2.
>>
>> There is one big fat patch called "gallivm,draw,llvmpipe: Support
>> wider native registers." [1] which makes backporting hard.
>> Jose?
>>
>> Regards,
>> - Sedat -
>>
>> [1] http://cgit.freedesktop.org/mesa/mesa/commit/?id=3469715
>>
>> P.S.: Patchset fixing build of mesa-8.0.5 with LLVM/CLANG v3.2
>>
>> [ gallium-auxiliary-fixes-for-8-0-5 (PENDING) ]
>> 4b7b71a rtti was removed from more llvm libraries. Thanks to d0k for
>> the hint via IRC #llvm on irc.oftc.net
>>
>> For more details see [1] and followup [2] discussion (Thanks Johannes
>> Obermayr again)!
>> [1]
>> http://lists.freedesktop.org/archives/mesa-dev/2012-October/029167.html
>> [2]
>> http://lists.freedesktop.org/archives/mesa-dev/2012-October/029184.html
>>
>> [ gallivm-fixes-for-8-0-5 (CHERRY-PICKED) ]
>> 920a940 gallivm: Fix createOProfileJITEventListener namespace with
>> llvm-3.1.
>> d998daf gallivm: Add constructor for raw_debug_ostream.
>> af1f68a gallivm: Add MCRegisterInfo.h to silence benign warnings about
>> missing implementation.
>> ad88aac gallivm: Pass in a MCInstrInfo to createMCInstPrinter on llvm-3.1.
>> 395c791 gallivm: Fix method overriding in raw_debug_ostream.
>> 557632f gallivm: Use InitializeNativeTargetDisassembler().
>> 6c0144a gallivm: Pass in a MCRegisterInfo to MCInstPrinter on llvm-3.1.
>> 1bb5b0d gallivm: Initialize x86 disassembler on x86_64 too.
>> 4d25e57 gallivm: Replace architecture test with PIPE_ARCH_*
>> 192859a gallivm: Fix LLVM-2.7 build.
>> 2dfd7e5 Initialize only native LLVM Disassembler.
>>
>> [ dri-nouveau-fixes-for-8-0-5 (CHERRY-PICKED) ]
>> abd8713 dri/nouveau: don't use nested functions
>>
>> - EOT -
>
>
> Why are you using mesa 8.0.5?  Wouldn't it be better to get into 9.x or
> master (aka 9.1)?
>

As pointed out in my other email, I am here on Ubuntu/precise AMD64
which runs mesa-8.0.x.
The simplest way was to install the so-called build-deps and build
mesa-8.0.5 after that.

Switching to a higher mesa-version results here in circular build-dependencies.
For example:
mesa-9.x wants a higher libdrm-version and I don't know what libdrm
requires for new build-deps to be resolved.
Finally, I have to bump my complete Linux graphics stack - I wanted to
avoid this!

- Sedat -

> -Brian
>


More information about the dri-devel mailing list