public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Richard Henderson <rth@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: splitting before sched2
Date: Sat, 04 Apr 1998 14:20:00 -0000	[thread overview]
Message-ID: <26056.891721317@hurl.cygnus.com> (raw)
In-Reply-To: <19980404120552.48484@dot.cygnus.com>

  In message < 19980404120552.48484@dot.cygnus.com >you write:
  > On Alpha at least there are a number of splits that are only enabled
  > after reload is complete.  I could have sworn other machines did this
  > as well.  My problem is that Haifa only tries splitting once, usually
  > before reload. 
Some machines do post reload splitting to help delay slot filling.

Recently (within the last year?) Joern added post reload splitting
to the old scheduler.  I thought I had merged up all the changes
to the old scheduler into hafia, but I must have missed that one.

          /* It is probably not worthwhile to try to split again in the
             second pass.  However, if flag_schedule_insns is not set,
             the first and only (if any) scheduling pass is after reload.  */
          if (reload_completed == 0 || ! flag_schedule_insns)           

I might argue that always splitting after reload would be a good
thing -- it would help some of the older PA7000 series machines
and there's also  a case where it would help the PA8000 series.


My vote would be to unconditionally split after reload for both
schedulers.

jeff

  reply	other threads:[~1998-04-04 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-04 16:52 Richard Henderson
1998-04-04 14:20 ` Jeffrey A Law [this message]
1998-04-04 17:48   ` Richard Henderson
1998-04-05 14:00     ` Joern Rennecke
1998-04-05 17:27       ` Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26056.891721317@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=rth@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).