Lines Matching defs:problem

40 /* Scanning is not really a dataflow problem, but it is useful to have
126 /* Allocate the problem specific data. */
129 /* This function is called if the problem has global data that needs
160 /* Function to massage the information after the problem solving. */
163 /* Function to free all of the problem specific datastructures. */
169 /* Function to add problem a dataflow problem that must be solved
170 before this problem can be solved. */
173 /* The static description of a dataflow problem to solve. See above
177 /* The unique id of the problem. This is used it index into
178 df->defined_problems to make accessing the problem data easy. */
200 /* The specific instance of the problem to solve. */
204 struct df_problem *problem; /* The problem to be solved. */
209 /* Array indexed by bb->index, that contains basic block problem and
231 /* Other problem specific data that is not on a per basic block
233 problem. The exception being the scanning problem where it is
337 Problem data for the scanning dataflow problem. Unlike the other
338 dataflow problems, the problem data for scanning is fully exposed and
339 used by owners of the problem.
348 nulls at the end of it. In PROBLEMS_BY_INDEX, the problem is
350 the problem local data without having to search the first
367 /* The following information is really the problem data for the
513 /* The results of the dataflow problem. */
529 /* The results of the dataflow problem. */
542 /* The results of the dataflow problem. */
556 /* The results of the dataflow problem. */
567 /* Kill and gen are defined as in the UR problem. */
571 /* The results of the dataflow problem. */