From: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
Message-Id: <199706021714.AA028481696@typhoon.rose.hp.com>
Subject: Re: New PGCC version available
To: ao950 AT FreeNet DOT Carleton DOT CA
Date: Mon, 02 Jun 1997 10:14:55 PDT
Cc: djgpp AT delorie DOT com
In-Reply-To: <5mr77b$jjo@freenet-news.carleton.ca>; from "Paul Derbyshire" at Jun 1, 97 7:09 am
Precedence: bulk

> Hopefully all the wrinkles are now ironed out. Will the pentium-optimizing
> gcc become the standard DJGPP gcc now?

I think most of the wrinkles are out.  At least, I haven't seen complaints
so far (I could have scared people off with the first release though :)

It will not be a standard DJGPP release.  Remember, it is based off of
the 2.7.2 snapshots, and then patched in addition to that.  Also,
it is very easy to crash.  Try compiling a floating point 
using program with -ffast-math -funroll-loops.  Watch it SIGFPE.
It is a development beta version, and will continue to be for some
time.  When 2.8 is released, I assume DJ will release that version.
PGCC will continue to be released as a patched 2.8 snapshot, since not
all of the optimizations have been accepted by the FSF ( I know the 
schedule-insns2 is the PCGs but aside from that not sure...).

> 
> (POV uses DJGPP?! I never knew that.)

The default DOS binary provided is compiled by Watcom.  The source 
distribution (for DOS) works with Watcom, Borland, DJGPP, and others.

> How did Pentium-optimized Allegro perform?
Slight improvement.

> (Would using PGCC affect Allegro much? Much of it, except the 3d stuff, is
> assembly.
Yep - PGCCs no help here 

> Is the assembly in Allegro's .S files pentium-optimal?)
Its pretty good assembly, but can be improved for pentium and pentium pro.