Lines Matching full:failure
275 /* Define how to allocate the failure stack. */
408 in case of failure. */
415 /* Throw away latest failure point and then jump to following
428 /* Jump to following two-byte address, and push a dummy failure
429 point. This failure point will be thrown away if an attempt
430 is made to use it for a failure. A `+' construct makes this
435 /* Push a dummy failure point and continue. Used at the end of
440 After matching N times, jump to the address upon failure. */
997 failure stack, but we would still use it for the register vectors;
1005 /* Failure stack declarations and macros; both re_compile_fastmap and
1006 re_match_2 use a failure stack. These have to be macros because of
1010 /* Number of failure points for which to initially allocate space
1017 /* Roughly the maximum number of failure points on the stack. Would be
1049 /* Define macros to initialize and free the failure stack.
1107 /* Push a pointer value onto the failure stack.
1113 /* This pushes an integer-valued item onto the failure stack.
1119 /* Push a fail_stack_elt_t value onto the failure stack.
1131 /* Used to omit pushing failure point id's when we're not debugging. */
1221 DEBUG_PRINT2 (" Pushing failure id: %u\n", failure_id); \
1231 #define NUM_NONREG_ITEMS 5 /* Includes failure point id. */
1273 /* Remove failure points and point to how many regs pushed. */ \
1281 DEBUG_PRINT2 (" Popping failure id: %u\n", failure_id); \
1346 failure stack. */
1906 push a failure point once, instead of every time
1934 /* On failure, jump from laststart to b + 3, which will be the
2256 { /* Push a dummy failure point at the end of the
2685 /* Initialize the failure stack to the largest possible stack. This
2693 is 2 * re_max_failures failure points. */
2941 /* We don't push any register information onto the failure stack. */
2950 /* This holds the pointer to the failure stack, when
3124 ordinary jump. For a * loop, it has pushed its failure
3295 found, -1 if no match, or -2 if error (such as failure
3568 failure stack overflowing). Otherwise, we return the length of the
3622 /* Failure point stack. Each place that can handle a failure further
3623 down the line pushes a failure point on this stack. It consists of
3628 scanning the strings. If the latter is zero, the failure point is
3629 a ``dummy''; if a failure happens and the failure point is a dummy,
3639 /* This holds the pointer to the failure stack, when
3686 This happens as we backtrack through the failure points, which in
3856 { /* More failure points to try. */
3875 /* If no failure points, don't restore garbage. And if
3979 DEBUG_PRINT4 ("%u failure points pushed, %u popped (%u remain).\n",
4225 by forcing a failure after pushing on the stack the
4319 /* Compare that many; failure if mismatch, else move
4439 a failure point to `p + mcnt' after we do this. */
4484 failure point which is what we will end up popping. */
4615 failure point. The pop_failure_jump takes off failure
4638 /* Unconditionally jump (without popping any failure points). */
4655 /* Normally, the on_failure_jump pushes a failure point, which
4668 /* At the end of an alternative, we need to push a dummy failure
4670 we don't want the failure point for the alternative to be
4882 /* If this failure point is a dummy, try the next one. */
4893 loop, need to pop this failure point and use the next one. */
4927 return -1; /* Failure to match. */
5334 routine will report only success or failure, and nothing about the
