public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI-SCI Drivers v1.1-7 released
Date: Tue, 6 Feb 2001 19:06:24 -0700	[thread overview]
Message-ID: <20010206190624.C23960@vger.timpanogas.org> (raw)
In-Reply-To: <20010206182501.A23454@vger.timpanogas.org>
In-Reply-To: <20010206182501.A23454@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Tue, Feb 06, 2001 at 06:25:01PM -0700

On Tue, Feb 06, 2001 at 06:25:01PM -0700, Jeff V. Merkey wrote:
> 
> Also, the GCC 2.96 compiler shipped with RedHat 7.1 is terribly 
> broken, and does not support #ident lines in the source code, 
> which also means that RedHat 7.1 will not work properly with 
> CVS (Code Versioning System) projects that use the #ident 
> keyword to identify and comment files.  It generates 
> an "unknown keyword" error message.  This version of the 
> sources disables some CVS enablement in order to build properly 
> on a RedHat 7.1 system with gcc 2.96.


More to add on the gcc 2.96 problems.  After compiling a Linux 2.4.1 
kernel on gcc 2.91, running SCI benchmarks, then compiling on RedHat 
7.1 (Fischer) with gcc 2.96, the 2.96 build DROPPED 30% in throughput
from the gcc 2.91 compiled version on the identical SAME 2.4.1 
source tree. 

I think RedHat should jetison gcc 2.96 as soon as possible...

Tests run on a PIII system limited to 90 MB/S PCI throughput.

gcc 2.91 on a PIII system in sci_copy mode           85 MB/S
gcc 2.96 in RedHat 7.1 (Fischer) in sci_copy mode    63 MB/S

Jeff


> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-07  1:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  1:25 PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
2001-02-07  2:06 ` Jeff V. Merkey [this message]
2001-02-07  2:07   ` [OT] " Gregory Maxwell
2001-02-07 18:08     ` Jeff V. Merkey
2001-02-07 17:32       ` Jakub Jelinek
2001-02-07 18:31         ` Jeff V. Merkey
2001-02-07 18:37           ` Tim Wright
2001-02-07 20:14             ` Jeff V. Merkey
2001-02-07 19:22               ` Alan Cox
2001-02-07 20:24                 ` Jeff V. Merkey
2001-02-07 20:35                   ` PCI-SCI Build Problems on RedHat 7.1 Jeff V. Merkey
2001-02-07 19:52                     ` Larry
2001-02-07  9:01   ` PCI-SCI Drivers v1.1-7 released David Howells
2001-02-07 18:10     ` Jeff V. Merkey
2001-02-07  9:22   ` Alan Cox
2001-02-07 18:19     ` Jeff V. Merkey
2001-02-07 19:06       ` Alan Cox
2001-02-07 20:03         ` Jeff V. Merkey
2001-02-07 19:12           ` Alan Cox
2001-02-07  9:15 ` Alan Cox
2001-02-07 18:13   ` Jeff V. Merkey
2001-02-07 19:02     ` Alan Cox
2001-02-07 20:02       ` Jeff V. Merkey

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=20010206190624.C23960@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=linux-kernel@vger.kernel.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