X-pop3-spooler:	POP3MAIL 2.1.0 b 4 980420 -bs-
Message-ID:	<19980902170442.12515@cerebro.laendle>
Date:	Wed, 2 Sep 1998 17:04:42 +0200
From:	Marc Lehmann <pcg AT goof DOT com>
To:	Steve Snyder <ssnyder AT indy DOT net>
Cc:	beastium <beastium-list AT Desk DOT nl>
Subject:	Re: pgcc-1.1a released
Mail-Followup-To:	Steve Snyder <ssnyder AT indy DOT net>,
	beastium <beastium-list AT desk DOT nl>
References:	<199809021140 DOT GAA16837 AT indy1 DOT indy DOT net>
Mime-Version:	1.0
In-Reply-To:	<199809021140.GAA16837@indy1.indy.net>; from Steve Snyder on Wed, Sep 02, 1998 at 07:37:32AM -0500
X-Operating-System:	Linux version 2.1.119 (root AT cerebro) (gcc version pgcc-2.91.54 19980816 (gcc2 ss-980609 experimental))
Status:	RO
Lines:	54

On Wed, Sep 02, 1998 at 07:37:32AM -0500, Steve Snyder wrote:
> On Wed, 2 Sep 1998 04:54:15 +0200, Marc Lehmann wrote:
> 
> >Please note that 1.1 is not yet announced. This was done to enable some
> >testing before the run on it begins, so prepare for an 1.1.1 version before
> >the end of this week (but the current 1.1 looks good, so don't _expect_ it)
> 
> Several questions:
> 
> 1. Will v1.1.x be made available in binary form, e.g. RedHat RPM packages?

You have to ask the binary maintainers, currently there are no provisions
for rpm (and personally I don't think rpm serve any purpose at all ;), but
if somebody would package it up (_preferably_ Andrew), I'd put it on the
server.

> 
> 2. On which version of EGCS is PGCC v1.1.x based?  Is it the recently 
> announced pre-release version of EGCS, or what?

Its based on egcs-1.1, not the prerelease.

> 3. What is the relationship of v1.1.x to recent PGCC snapshots?  That is, 
> is v1.1.x the same as (egcs-19980824 + pgcc-patch-19980824) with the 
> developers now confident of its stability?

My usual routine is to publish pgcc based on, and with the same version
number, as egcs. So, unless otherwise noted, every pgcc version is based on
the egcs version with the same version number.

egcs (and thus pgcc) has been tracking the 1.1 release branch for some time
now, after the release pgcc snapshots will be based on egcs again.

All bugs currently found in pgcc fall into these groups:

- real BUGS (very seldom)
- real "bugs" that cause pgcc to compile ISO-C code and gcc extensions properly,
  but not various hacks (kernels...). I don't fix these, but as soon as egcs
  supersedes these optimizations (which is actively being worked on), they will
  be disabled.
- bugs in egcs that are only visible in pgcc
- incompatibilities between egcs and pgcc, causing bugs in pgcc. These will be
  resolved as soon as possible.
- correct code, but horrible performance. egcs does perform worse than 2.7.2 in
  some cases, and pgcc follows this.
- anything else I forgot... ;)

      -----==-                                              |
      ----==-- _                                            |
      ---==---(_)__  __ ____  __       Marc Lehmann       +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com       |e|
      -=====/_/_//_/\_,_/ /_/\_\                          --+
    The choice of a GNU generation                        |
                                                          |

- Raw text -