From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: PA port & haifa
Date: Tue, 19 Aug 1997 22:15:40 -0000 [thread overview]
Message-ID: <33FA0E96.630@shellus.com> (raw)
Message-ID: <19970819221540.RumNpmOvW7UZHOOE-z0I_zlUezIObsuljEpwCvsBgUg@z> (raw)
In the next snapshot, the PA port will default to using the
haifa scheduler.
After some tuning of the PA backend, haifa is showing a noticable
improvement in FP intensive code. While there are still some
cases where the generated code is slower, the majority of the
time the code is significantly faster. For specfp92 I'm seeing
an overall improvement of about 6.5%.
I encourage others to test with haifa and tune the scheduling
parameters to get good performance from haifa.
As haifa improves in both code reliability and speed, we can
make it the default for additional cpus -- with the goal of
having the haifa scheduler replace the old scheduler.
Jeff
next reply other threads:[~1997-08-19 22:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 21:22 Ian Haggard [this message]
1997-08-19 22:15 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-08-19 19:24 Ugly *.def in gcc H.J. Lu
1997-08-19 19:45 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 19:12 H.J. Lu
1997-08-19 19:00 H.J. Lu
1997-08-19 19:00 ` Jeffrey A Law
1997-08-19 19:00 Some Haifa scheduler bugs Jeffrey A Law
1997-08-19 19:00 ` A prototype patch for tree.h/tree.def/calls.c H.J. Lu
1997-08-19 19:00 ` Jeffrey A Law
1997-08-19 17:54 H.J. Lu
1997-08-19 17:52 John Carr
1997-08-19 17:43 D.V. Henkel-Wallace
1997-08-19 16:06 egcs: A new compiler project to merge the existing GCC forks H.J. Lu
1997-08-19 16:06 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 13:19 H.J. Lu
1997-08-19 3:52 egcs: A new compiler project to merge the existing GCC forks (fwd) H.J. Lu
1997-08-19 5:08 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-18 23:56 H.J. Lu
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=33FA0E96.630@shellus.com \
--to=law@hurl.cygnus.com \
--cc=egcs@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).