From: Ronald Wahl <Ronald.Wahl@informatik.tu-chemnitz.de>
To: Marc Lehmann <pcg@goof.com>
Cc: egcs@cygnus.com
Subject: pgcc/egcs/gcc benchmarks on a K6-200
Date: Wed, 10 Dec 1997 12:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.971210204733.28941A-101000@goliath.csn.tu-chemnitz.de> (raw)
In-Reply-To: <19971210184221.31026@cerebro.laendle>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi,
A attached a gzipped file with some benchmarks (nbench) I made on
a K6-200 with pgcc-1.0 (based on egcs-1.0), egcs-1.0 and the gcc-2.7.2.3
from the FSF. The benchmarks show that we can improve optimization of
pgcc/egcs for a K6. It's interesting to see that the FSF gcc is faster on
some benches than pgcc and egcs. I hope someone will work on it to get
better K6 optimization. If I could help (not code hacking but testing)
just let me know...
ron
--
\ Ronald Wahl --- rwa@informatik.tu-chemnitz.de \
\ WWW: http://www.tu-chemnitz.de/~row \
\ Talk: rwa@goliath.csn.tu-chemnitz.de \
\ PGP key available by finger to my email address \
[-- Attachment #2: nbm_compare.txt.gz --]
[-- Type: application/x-gzip, Size: 2991 bytes --]
parent reply other threads:[~1997-12-10 12:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <19971210184221.31026@cerebro.laendle>]
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.LNX.3.96.971210204733.28941A-101000@goliath.csn.tu-chemnitz.de \
--to=ronald.wahl@informatik.tu-chemnitz.de \
--cc=egcs@cygnus.com \
--cc=pcg@goof.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).