This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: A new patch for floating point conditional mov on PPo
- To: hjl at lucon dot org
- Subject: Re: A new patch for floating point conditional mov on PPo
- From: john at feith dot com (John Wehle)
- Date: Tue, 9 Jun 1998 22:53:13 -0400
- Cc: egcs-patches at cygnus dot com
1) What prevents gcc from accidently matching the fcmov test / compare
insns by adding a clobber to an existing compare insn? There's a note
in md.texi about the combiner adding / deleting clobber expressions
as necessary.
2) In output_int_test_compare_fcmov you have:
if (CONSTANT_P (operands[0]) || GET_CODE (operands[1]) == MEM)
output = reverse;
else
output = normal;
a) I believe that the patterns require operand 0 to be a
nonimmediate_operand in which case how can CONSTANT_P
ever be true?
b) I believe that Intel allows operand 1 to be a memory
operand in which case why does anything special need
to be done?
-- John
-------------------------------------------------------------------------
| Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com |
| John Wehle | Fax: 1-215-540-5495 | |
-------------------------------------------------------------------------