summaryrefslogtreecommitdiff
path: root/gcc/jump.c
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2001-08-13 08:27:08 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2001-08-13 08:27:08 +0000
commit85fc0ad11d438d9d2ac6553176dc00f4ad06381d (patch)
tree1ce1321ac3b9c93d610003f06c507e1989c48d8d /gcc/jump.c
parentd24eb4d18e08f9c3a5c4249165773d2e38b7cfcc (diff)
downloadgcc-85fc0ad11d438d9d2ac6553176dc00f4ad06381d.tar.gz
* jump.c: Fix formatting.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@44846 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/jump.c')
-rw-r--r--gcc/jump.c56
1 files changed, 28 insertions, 28 deletions
diff --git a/gcc/jump.c b/gcc/jump.c
index 9099c1f5c3a..0b62ab42114 100644
--- a/gcc/jump.c
+++ b/gcc/jump.c
@@ -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. */