Re: Selective scheduling pass - target changes (ia64 & rs6000) [3/3]

["David Edelsohn" <dje.gcc@gmail.com>]

	* config/rs6000/rs6000.c (rs6000_init_sched_context,
	rs6000_alloc_sched_context, rs6000_set_sched_context,
	rs6000_free_sched_context): New functions.
	(struct _rs6000_sched_context): New.
	(rs6000_sched_reorder2): Do not modify INSN_PRIORITY for selective
	scheduling.
	(rs6000_sched_finish): Do not run for selective scheduling.

The rs6000 part of the patch is okay with a modification to the following chunk:

*************** rs6000_sched_finish (FILE *dump, int sch
*** 20085,20091 ****

    if (reload_completed && rs6000_sched_groups)
      {
!       if (rs6000_sched_insert_nops == sched_finish_none)
        return;

        if (rs6000_sched_insert_nops == sched_finish_pad_groups)
--- 20103,20110 ----

    if (reload_completed && rs6000_sched_groups)
      {
!       if (rs6000_sched_insert_nops == sched_finish_none
!         || sel_sched_p ())
        return;

        if (rs6000_sched_insert_nops == sched_finish_pad_groups)


Please change this to a separate test for clarify

+       /* Do not run sched_finish hook when selective scheduling enabled.  */
+       if (sel_sched_p ())
+        return;
+
        if (rs6000_sched_insert_nops == sched_finish_none)
          return;

instead of combining the tests.


Also, target maintainers have flexibility during stage 3 with respect
to changes local to a port,
so the Itanium changes can be approved and committed during stage 3,
although earlier would
be better.

Thanks, David