Am 18.09.2017 um 19:11 schrieb Roland Scheidegger:
> Am 18.09.2017 um 17:36 schrieb Nicolai Hähnle:
>> On 18.09.2017 17:02, Roland Scheidegger wrote:
>>> This looks like a horrendous solution which will break the world - well
>>> for us :-). Because integers simply will cease to work, always flushe
Am 18.09.2017 um 17:36 schrieb Nicolai Hähnle:
> On 18.09.2017 17:02, Roland Scheidegger wrote:
>> This looks like a horrendous solution which will break the world - well
>> for us :-). Because integers simply will cease to work, always flushed
>> to zero (bye bye loop counter...).
>> The reason is
On 18.09.2017 17:02, Roland Scheidegger wrote:
This looks like a horrendous solution which will break the world - well
for us :-). Because integers simply will cease to work, always flushed
to zero (bye bye loop counter...).
The reason is that when you translate from something with a untyped
regi
This looks like a horrendous solution which will break the world - well
for us :-). Because integers simply will cease to work, always flushed
to zero (bye bye loop counter...).
The reason is that when you translate from something with a untyped
register file to something typed, the obvious solutio
Hi all,
This series fixes an issue we have on GCN due to the arguably inconsistent
handling of denormal floating point values. We disable denormals for 32-bit
floating point numbers, because enabling them would cost a lot of
performance. By and large, GCN floating point instructions flush denormal
