public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: egcs: A new compiler project to merge the existing GCC forks (fwd)
Date: Tue, 19 Aug 1997 17:54:31 -0000	[thread overview]
Message-ID: <9708191546.AA21698@moene.indiv.nluug.nl> (raw)
Message-ID: <19970819175431.3nnJaGezD_axb8xe6QWkquUsykwGbv9tq-mQiJY4UsE@z> (raw)
In-Reply-To: Tue, 19 Aug 1997 00:01:28 -0600"

>>>>> "Jeffrey" == Jeffrey A Law <law@hurl.cygnus.com> writes:

 Jeffrey> Could be -- I don't think gcc-2.7* scheduled instructions on
 Jeffrey> the x86 machines at all.

FWIW, the last gcc2 snapshot I could build (with -m586 in) typically
seemed to gain about 20% on a 586 with single-precision Fortran code,
roughly consistent with numbers reported by proprietary offerings at
the time, though some with `pentium optimization' only seemed to
perform about as well as the gcc-2.7-based g77 (generating 486 code).

If people care about Fortran performance I'll eventually do some
realistic tests on a 586, but have no access to a 686; this isn't
necessarily trivial, though, and I'm more interested in the release of
a correct g77 0.5.21 at this stage.

             reply	other threads:[~1997-08-19 17:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-19 17:54 Jeffrey A Law [this message]
1997-08-19 17:54 ` Dave Love
1997-08-19 17:54 ` egcs: A new compiler project to merge the existing GCC forks Toon Moene
  -- strict thread matches above, loose matches on Subject: below --
1997-09-04 11:27 Some Haifa scheduler bugs meissner
     [not found] <Pine.SOL.3.90.970826141030.2901K-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:42 ` Jeffrey A Law
     [not found] <Pine.SOL.3.90.970826140826.2901J-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:33 ` Jeffrey A Law
1997-09-03  9:30   ` Bernd Schmidt
1997-09-03  9:37     ` Jeffrey A Law
1997-09-03  9:44       ` Bernd Schmidt
1997-09-03 10:07         ` Jeffrey A Law
1997-09-05  7:15           ` Bernd Schmidt
1997-09-05  7:55             ` Jeffrey A Law
1997-09-05  8:33             ` Ian Lance Taylor
1997-09-03 11:58       ` Jim Wilson
1997-09-03 11:39     ` Paul Koning
1997-09-03 11:50       ` David Edelsohn
1997-09-03 13:13       ` Richard Henderson
1997-09-03 13:19       ` Jeffrey A Law
1997-09-04  9:33         ` Craig Burley
1997-09-04 11:12           ` Jeffrey A Law
1997-09-04 11:33             ` David S. Miller
1997-09-04 14:38               ` David Edelsohn
1997-08-26 14:34 Bernd Schmidt
1997-08-22 13:53 Building of generated parser files Andreas Schwab
1997-08-22 15:02 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-22 15:24 ` Jeffrey A Law
1997-08-22 10:48 Building of generated parser files Niklas Hallqvist
1997-08-22 13:28 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:43 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-21 15:20 egcs repository Joel Sherrill
1997-08-21 15:47 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-19 19:00 Jeffrey A Law
1997-08-19  7:36 egcs: A new compiler project to merge the existing GCC forks (fwd) Robert Wilhelm
1997-08-19  9:34 ` Some Haifa scheduler bugs Bernd Schmidt

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=9708191546.AA21698@moene.indiv.nluug.nl \
    --to=d.love@dl.ac.uk \
    --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).