-static ir_node *add_to_sched(block_sched_env_t *env, ir_node *irn)
-{
- /* If the node consumes/produces data, it is appended to the schedule
- * list, otherwise, it is not put into the list */
- if (must_appear_in_schedule(env->selector, env->selector_block_env, irn)) {
- sched_info_t *info = get_irn_sched_info(irn);
- INIT_LIST_HEAD(&info->list);
- info->scheduled = 1;
- update_sched_liveness(env, irn);
- sched_add_before(env->block, irn);
-
- DBG((env->dbg, LEVEL_2, "\tadding %+F\n", irn));
- }
-
- /* notify the selector about the finally selected node. */
- if (env->selector->node_selected)
- env->selector->node_selected(env->selector_block_env, irn);
-
- /* Insert the node in the set of all already scheduled nodes. */
- mark_already_scheduled(env, irn);
-
- /* Remove the node from the ready set */
- if(nodeset_find(env->cands, irn))
- nodeset_remove(env->cands, irn);
-
- return irn;
-}
-
-/**
- * Add the proj nodes of a tuple-mode irn to the schedule immediately
- * after the tuple-moded irn. By pinning the projs after the irn, no
- * other nodes can create a new lifetime between the tuple-moded irn and
- * one of its projs. This should render a realistic image of a
- * tuple-moded irn, which in fact models a node which defines multiple
- * values.
- *
- * @param irn The tuple-moded irn.
- */
-static void add_tuple_projs(block_sched_env_t *env, ir_node *irn)