On 01/25/2017 01:42 PM, Francisco Jerez wrote:
> Ian Romanick writes:
>
>> On 01/24/2017 03:26 PM, Francisco Jerez wrote:
>>> This does point at the front-end emitting silly code that could have
>>> been optimized out, but the current fsign implementation would emit
>>> bogus IR if abs was set fo
Ian Romanick writes:
> On 01/24/2017 03:26 PM, Francisco Jerez wrote:
>> This does point at the front-end emitting silly code that could have
>> been optimized out, but the current fsign implementation would emit
>> bogus IR if abs was set for the argument (because it would apply the
>> abs modif
On 01/24/2017 03:26 PM, Francisco Jerez wrote:
> This does point at the front-end emitting silly code that could have
> been optimized out, but the current fsign implementation would emit
> bogus IR if abs was set for the argument (because it would apply the
> abs modifier on an unsigned integer ty
This does point at the front-end emitting silly code that could have
been optimized out, but the current fsign implementation would emit
bogus IR if abs was set for the argument (because it would apply the
abs modifier on an unsigned integer type), and we shouldn't rely on
the upper layer's optimiz
