On 19 September 2017 at 15:23, Vedran Miletić wrote:
> On 09/18/2017 06:00 PM, Emil Velikov wrote:
>> Hi all,
>>
>> As you may know, different components in Mesa use LLVM for various purposes.
>>
>> In particular:
>> - 3.3.0 for the aux gallium module, gallivm
>> - 3.6.0 for the opencl state-tra
On Tue, Sep 19, 2017 at 9:23 AM, Vedran Miletić wrote:
> On 09/18/2017 06:00 PM, Emil Velikov wrote:
>> Hi all,
>>
>> As you may know, different components in Mesa use LLVM for various purposes.
>>
>> In particular:
>> - 3.3.0 for the aux gallium module, gallivm
>> - 3.6.0 for the opencl state-t
On 09/18/2017 06:00 PM, Emil Velikov wrote:
> Hi all,
>
> As you may know, different components in Mesa use LLVM for various purposes.
>
> In particular:
> - 3.3.0 for the aux gallium module, gallivm
> - 3.6.0 for the opencl state-tracker, clover
> - 3.9.0 for multiple drivers r600, radeonsi,
On Mon, 2017-09-18 at 17:00 +0100, Emil Velikov wrote:
> Hi all,
>
> As you may know, different components in Mesa use LLVM for various purposes.
>
> In particular:
> - 3.3.0 for the aux gallium module, gallivm
> - 3.6.0 for the opencl state-tracker, clover
> - 3.9.0 for multiple drivers r600,
Hi all,
As you may know, different components in Mesa use LLVM for various purposes.
In particular:
- 3.3.0 for the aux gallium module, gallivm
- 3.6.0 for the opencl state-tracker, clover
- 3.9.0 for multiple drivers r600, radeonsi, radv and swr
AFAICT gallivm is build on Windows, and using