Home | History | Annotate | Download | only in gcc

Lines Matching refs:constraints

617      constraints for the two operands can be completely
618      different.  (Indeed, if the constraints for the two
622       && recog_data.constraints[use][0] == '%')
627       && recog_data.constraints[use - 1][0] == '%')
636    constraints of alternative ALT.
642        constraints.
644    (2) DEF matches (via 0-9 constraints) an operand that is an
733 		  && recog_data.constraints[use][0] == '%'
736 		  && recog_data.constraints[use - 1][0] == '%'
769    checking classes of the constraints and pseudos because otherwise
846 /* Checks that CONSTRAINTS permits to use only one hard register.  If
850 single_reg_class (const char *constraints, rtx op, rtx equiv_const)
858   while ((c = *constraints))
871 	    /* ??? Is this the best way to handle memory constraints?  */
872 	    cn = lookup_constraint (constraints);
898 	      unsigned long dup = strtoul (constraints, &end, 10);
899 	      constraints = end;
901 		= single_reg_class (recog_data.constraints[dup],
912       constraints += CONSTRAINT_LEN (c, constraints);
925   return single_reg_class (recog_data.constraints[op_num],
930    might be used by insn reloads because the constraints are too
952 	  const char *p = recog_data.constraints[i];