<div dir="ltr">No, we don't support these options, and I don't think we'll want to implement -mno-fp-ret-in-387. To my knowledge, nobody actually needs to return floating point values in GPRs. What the Linux kernel probably wants is to completely disable floating point. In an ideal world, both gcc and clang would grow an -f[no-]floating-point flag, which would reject floating point code in the frontend.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 2:37 AM, Jan-Simon Möller <span dir="ltr"><<a href="mailto:dl9pf@gmx.de" target="_blank">dl9pf@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi !<br>
<br>
Are there options similar to:<br>
<br>
-mno-80387:<br>
<br>
On machines where a function returns floating-point results in the<br>
80387<br>
register stack, some floating-point opcodes may be emitted even if<br>
-msoft-float is used.<br>
<br>
-mno-fp-ret-in-387<br>
Do not use the FPU registers for return values of functions.<br>
<br>
The usual calling convention has functions return values of types<br>
"float"<br>
and "double" in an FPU register, even if there is no FPU. The idea<br>
is that<br>
the operating system should emulate an FPU.<br>
<br>
The option -mno-fp-ret-in-387 causes such values to be returned in<br>
ordinary<br>
CPU registers instead.<br>
<br>
<br>
Or what combination of flags makes sure we won't hit these quirks in the first<br>
place ?<br>
<br>
Thanks.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
<br>
Dipl.-Ing.<br>
Jan-Simon Möller<br>
<br>
<a href="mailto:jansimon.moeller@gmx.de">jansimon.moeller@gmx.de</a><br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</font></span></blockquote></div><br></div>