mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2025-04-22 11:31:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

* jump.c: Fix formatting.

Browse Source 
From-SVN: r44846
This commit is contained in:
Kazu Hirata 2001-08-13 08:27:08 +00:00 committed by Kazu Hirata
parent 7ba7767b1c
commit 5d0cab94d0
2 changed files with 32 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gcc/ChangeLog
View File

@ -1,3 +1,7 @@
2001-08-13 Kazu Hirata <kazu@hxi.com>
* jump.c: Fix formatting.
2001-08-13 Kazu Hirata <kazu@hxi.com>
* config/h8300/h8300.md (zero_extendqihi2): Correct the insn

56
gcc/jump.c
View File

@ -653,40 +653,40 @@ reversed_comparison_code_parts (code, arg0, arg1, insn)
&& REVERSIBLE_CC_MODE (mode))
{
#ifdef REVERSE_CONDITION
return REVERSE_CONDITION (code, mode);
return REVERSE_CONDITION (code, mode);
#endif
return reverse_condition (code);
}
return reverse_condition (code);
}
#endif
/* Try a few special cases based on the comparison code. */
switch (code)
{
case GEU:
case GTU:
case LEU:
case LTU:
case NE:
case EQ:
/* It is always safe to reverse EQ and NE, even for the floating
point. Similary the unsigned comparisons are never used for
floating point so we can reverse them in the default way. */
return reverse_condition (code);
case ORDERED:
case UNORDERED:
case LTGT:
case UNEQ:
/* In case we already see unordered comparison, we can be sure to
be dealing with floating point so we don't need any more tests. */
return reverse_condition_maybe_unordered (code);
case UNLT:
case UNLE:
case UNGT:
case UNGE:
/* We don't have safe way to reverse these yet. */
return UNKNOWN;
default:
break;
case GEU:
case GTU:
case LEU:
case LTU:
case NE:
case EQ:
/* It is always safe to reverse EQ and NE, even for the floating
point. Similary the unsigned comparisons are never used for
floating point so we can reverse them in the default way. */
return reverse_condition (code);
case ORDERED:
case UNORDERED:
case LTGT:
case UNEQ:
/* In case we already see unordered comparison, we can be sure to
be dealing with floating point so we don't need any more tests. */
return reverse_condition_maybe_unordered (code);
case UNLT:
case UNLE:
case UNGT:
case UNGE:
/* We don't have safe way to reverse these yet. */
return UNKNOWN;
default:
break;
}
/* In case we give up IEEE compatibility, all comparisons are reversible. */