On 11/03/14 01:11, Jan Beulich wrote:
I really don't like having an option that's globally applied for this
feature. THough I am OK with having a mechanism to avoid implicit
clobbers on specific ASMs.
Why not? That way, for projects/components knowing all their
asm()s have all clobbers explici
>>> On 31.10.14 at 20:02, wrote:
> On 10/31/14 02:07, Jan Beulich wrote:
>> While it always seemed wrong to me that there's no way to avoid the
>> default "flags" and "fpsr" clobbers, the regression the fix for
>> PR/60663 introduced (see PR/63637) makes it even more desirable to have
>> such a me
On 10/31/14 02:07, Jan Beulich wrote:
While it always seemed wrong to me that there's no way to avoid the
default "flags" and "fpsr" clobbers, the regression the fix for
PR/60663 introduced (see PR/63637) makes it even more desirable to have
such a mechanism: This way, at least asm()s with a sing
While it always seemed wrong to me that there's no way to avoid the
default "flags" and "fpsr" clobbers, the regression the fix for
PR/60663 introduced (see PR/63637) makes it even more desirable to have
such a mechanism: This way, at least asm()s with a single output and no
explicit clobbers can a
