public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjstein@bfr.co.il (Harvey J. Stein)
To: Richard Henderson <rth@cygnus.com>
Cc: hjstein@blinky.bfr.co.il
Subject: Re: EGCS vs GCC performance
Date: Tue, 20 Jan 1998 02:21:00 -0000	[thread overview]
Message-ID: <m24t2zbimz.fsf@blinky.bfr.co.il> (raw)
In-Reply-To: <19980119092950.01394@dot.cygnus.com>

Richard Henderson <rth@cygnus.com> writes:

> On Sun, Jan 18, 1998 at 10:11:43AM +0200, Harvey J. Stein wrote:
> > What about on the Alphas?  Is the Haifa scheduler configured properly
> > for the Dec Alpha?  Or is one better off currently disabling Haifa?
> 
> It is configured properly for EV5 machines for certain. 

What about EV56s?  I presume that the same config would be fine?  And
as of what date is the above the case?  With egcs-1.0 on redhat 4.2 I
found egcs producing code which ran about the same as gcc 2.7.2.1,
sometimes a little slower (-O2 -mcpu=21164).  I tried to build
egcs-971225 & pre 1.0.1, but was unable to (because redhat 4.2's
binutils (v 2.7.0.2-4) was too old, I guess).  Presumably, for the
same reason I couldn't use -mcpu=21164a with egcs-971225.  How much of
a difference does -mcpu=21164 vs -mcpu=21164a make?

Thanks,

Harvey J. Stein
Berger Financial Research
hjstein@bfr.co.il

  reply	other threads:[~1998-01-20  2:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12 20:31 Dave Steffen
1998-01-14  4:17 ` jbuck
1998-01-15 16:06   ` David Edelsohn
1998-01-15 16:30   ` Jeffrey A Law
1998-01-17 23:02     ` Marc Lehmann
1998-01-18 21:51     ` Harvey J. Stein
1998-01-18  0:13       ` Jeffrey A Law
1998-01-19 10:12       ` Richard Henderson
1998-01-20  2:21         ` Harvey J. Stein [this message]
1998-01-20 10:07           ` Richard Henderson
1998-01-20 14:54           ` Toon Moene
1998-01-20 14:54             ` 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=m24t2zbimz.fsf@blinky.bfr.co.il \
    --to=hjstein@bfr.co.il \
    --cc=hjstein@blinky.bfr.co.il \
    --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).