On Mon, 24 Feb 2014, Richard Biener wrote:
Well, your asm cannot modify it as you don't have a use or clobber for FP
state (but there isn't any...).
Ah, right, I was focusing on "volatile" and forgot there is no "memory"
clobber in those asms, cool, that may simplify things a lot.
Also I thi
On Mon, Feb 24, 2014 at 1:43 PM, Marc Glisse wrote:
> On Mon, 24 Feb 2014, Richard Biener wrote:
>
>> On Sun, Feb 23, 2014 at 12:09 PM, Marc Glisse
>> wrote:
>>>
>>> Hello,
>>>
>>> a natural first step to optimize changes of rounding modes seems to be
>>> making these 2 functions builtins. I don'
On Mon, 24 Feb 2014, Richard Biener wrote:
On Sun, Feb 23, 2014 at 12:09 PM, Marc Glisse wrote:
Hello,
a natural first step to optimize changes of rounding modes seems to be
making these 2 functions builtins. I don't know exactly how far
optimizations will be able to go (the fact that fesetro
On Mon, Feb 24, 2014 at 10:02 AM, Richard Biener
wrote:
> On Sun, Feb 23, 2014 at 12:09 PM, Marc Glisse wrote:
>> Hello,
>>
>> a natural first step to optimize changes of rounding modes seems to be
>> making these 2 functions builtins. I don't know exactly how far
>> optimizations will be able to
On Sun, Feb 23, 2014 at 12:09 PM, Marc Glisse wrote:
> Hello,
>
> a natural first step to optimize changes of rounding modes seems to be
> making these 2 functions builtins. I don't know exactly how far
> optimizations will be able to go (the fact that fesetround can fail
> complicates things a lo
Hello,
a natural first step to optimize changes of rounding modes seems to be
making these 2 functions builtins. I don't know exactly how far
optimizations will be able to go (the fact that fesetround can fail
complicates things a lot). What is included here:
1) fegetround is pure.
2) Neith