From: "M.V.S. Phani Narasimham" <phanimvs@wipinfo.soft.net>
To: gcc-help@gcc.gnu.org
Subject: Re.Scheduler
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.1000316091653.3344A-100000@gem> (raw)
Message-ID: <20000401000000.SGce1CVLJK6k4yoi2TeWQcBp2NXN_1GnLD1aqrg2sKY@z> (raw)
hai,
Why does the gcc instruction scheduler does the scheduling from
bottom to top (considering single basic block it schdules from
tail to head). Is there any specific reason to it.
My argument is when we calculate all the dependencies
we can find the insns independent at a particular instant
and schedule them.
Even some of the papers i looked do list-scheduling from top
to bottom.
One reference:
Instruction scheduling for IBM RISC System/6000 processor
IBM Research journal 1900
sincierly,
phani.
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 19:57 M.V.S. Phani Narasimham [this message]
2000-04-01 0:00 ` Re.Scheduler M.V.S. Phani Narasimham
2000-07-26 22:48 Re.Scheduler phani narasimhan venkata sesha myreddy
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=Pine.GSO.3.96.1000316091653.3344A-100000@gem \
--to=phanimvs@wipinfo.soft.net \
--cc=gcc-help@gcc.gnu.org \
/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).