contrib/gcc/fold-const.c

153    sign.  Use `^' to test whether signs differ, and `< 0' to isolate the
2622    it does not test whether they are equal using C's == operation.
2681 	 Might as well play it safe and always test this.  */
2759 /* Define macros to test an operand from arg0 and arg1 for equality and a
3044 	 one side of the comparison is each of the values; test for the
3598      this not only for its own sake, but to avoid having to test for this
3773    or zero extension, also test VAL against the unextended type.
3856    try to change a logical combination of comparisons into a range test.
4043 	     range tests.  We test arg0_type since often the return type
4242    type, TYPE, return an expression to test if EXP is in (or out of, depending
4243    on IN_P) the range.  Return 0 if the test couldn't be created.  */
4906    merge it into some range test.  Return the new tree if so.  */
4920 				  "when simplifying range test");
4928      can build the range test, return it or it inverted.  If one of the
6024   tree test, true_value, false_value;
6036       test = TREE_OPERAND (cond, 0);
6050       test = cond;
6073   test = fold_build3 (COND_EXPR, type, test, lhs, rhs);
6074   return fold_convert (type, test);
6490    equality/inequality test, then return a simplified form of the test
6498   /* If this is testing a single bit, we can optimize the test.  */
6524    equality/inequality test, then return a simplified form of
6525    the test using shifts and logical operations.  Otherwise return
6532   /* If this is testing a single bit, we can optimize the test.  */
6545       /* First, see if we can fold the single bit test into a sign-bit
6546 	 test.  */
8452      into a single range test.  */
10635 	     all we need to do is test pointer equality for the arguments
10638 	     C equality test.  It can in fact return false for two
10639 	     objects which would test as equal using the C equality
12768       /* We used to test for !integer_zerop here.  This does not work correctly