On 09/02/15 23:25, Sedat Dilek wrote:
On Mon, Feb 9, 2015 at 9:51 PM, Jose Fonseca wrote:
On 09/02/15 17:44, Emil Velikov wrote:
Hi Sedat,
On 07/02/15 22:42, Sedat Dilek wrote:
[ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
Hi,
I already reported this when playing 1st t
On Mon, Feb 9, 2015 at 6:44 PM, Emil Velikov wrote:
> Hi Sedat,
>
> On 07/02/15 22:42, Sedat Dilek wrote:
>> [ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
>>
>> Hi,
>>
>> I already reported this when playing 1st time with my llvm-toolchain
>> v3.6.0rc2 and mesa v10.3.7 [1].
>> T
On Mon, Feb 9, 2015 at 9:51 PM, Jose Fonseca wrote:
> On 09/02/15 17:44, Emil Velikov wrote:
>>
>> Hi Sedat,
>>
>> On 07/02/15 22:42, Sedat Dilek wrote:
>>>
>>> [ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
>>>
>>> Hi,
>>>
>>> I already reported this when playing 1st time with m
On 09/02/15 17:44, Emil Velikov wrote:
Hi Sedat,
On 07/02/15 22:42, Sedat Dilek wrote:
[ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
Hi,
I already reported this when playing 1st time with my llvm-toolchain
v3.6.0rc2 and mesa v10.3.7 [1].
The issue still remains in mesa v10.
Hi Sedat,
On 07/02/15 22:42, Sedat Dilek wrote:
> [ Please CC me I am not subscribed to mesa-dev and llvmdev MLs ]
>
> Hi,
>
> I already reported this when playing 1st time with my llvm-toolchain
> v3.6.0rc2 and mesa v10.3.7 [1].
> The issue still remains in mesa v10.4.4.
>
> So, this is a fiel
On Sun, Feb 8, 2015 at 12:04 AM, Jose Fonseca wrote:
> I think we decided not to support unreleased LLVM builds on stable releases.
>
> This is because building without errors is not enough -- there are often
> other changes that need to go with this. Furthermore it's often a moving
> target.
>
>
Just as a hint:
You need to cherry-pick...
commit ef7e0b39a24966526b102643523feac765771842
"gallivm: Update for RTDyldMemoryManager becoming an unique_ptr."
...from mesa upstream to build v10.4.4 successfully.
- Sedat -
On Sat, Feb 7, 2015 at 11:42 PM, Sedat Dilek wrote:
> [ Please CC me I a
I think we decided not to support unreleased LLVM builds on stable releases.
This is because building without errors is not enough -- there are often
other changes that need to go with this. Furthermore it's often a moving
target.
In short, if you want to use bleeding edge LLVM, you must use
