On 11/25/13 3:00 PM, Iain Buclaw wrote:
On 25 November 2013 20:34, Iain Buclaw wrote:
On 25 November 2013 19:35, Brad Roberts wrote:
On 11/25/13 2:35 AM, Iain Buclaw wrote:
On 25 November 2013 10:32, Iain Buclaw wrote:
Yep, there's been some middle-end changes. Sorry, next time I'll gi
On 25 November 2013 20:34, Iain Buclaw wrote:
> On 25 November 2013 19:35, Brad Roberts wrote:
>> On 11/25/13 2:35 AM, Iain Buclaw wrote:
>>>
>>> On 25 November 2013 10:32, Iain Buclaw wrote:
Yep, there's been some middle-end changes. Sorry, next time I'll give
you heads up.
On 25 November 2013 19:35, Brad Roberts wrote:
> On 11/25/13 2:35 AM, Iain Buclaw wrote:
>>
>> On 25 November 2013 10:32, Iain Buclaw wrote:
>>>
>>>
>>> Yep, there's been some middle-end changes. Sorry, next time I'll give
>>> you heads up.
>>>
>>> ...Which, incidentally, might come very soon, a
On 11/25/13 2:35 AM, Iain Buclaw wrote:
On 25 November 2013 10:32, Iain Buclaw wrote:
Yep, there's been some middle-end changes. Sorry, next time I'll give
you heads up.
...Which, incidentally, might come very soon, as there are some other
front-end breaking changes in the pipeline with a ne
On 25 November 2013 09:00, Brad Roberts wrote:
> I noticed that the GDC auto-tester failed the most recent build cycle. I
> assumed it was due to having an old snapshot. After updating it, the build
> failed in the same way.
>
> The 'old' snapshot: GCC_VER=4.9-20130929
> The one it's running no
On 25 November 2013 10:32, Iain Buclaw wrote:
> On 25 November 2013 09:00, Brad Roberts wrote:
>> I noticed that the GDC auto-tester failed the most recent build cycle. I
>> assumed it was due to having an old snapshot. After updating it, the build
>> failed in the same way.
>>
>> The 'old' sna
