Date: Fri, 5 Mar 1999 11:06:12 +0100
To: pgcc AT delorie DOT com
Subject: Re: problems with pgcc and linux kernel module (2.2.x)
Message-ID: <19990305110612.D353@cerebro.laendle>
Mail-Followup-To: pgcc AT delorie DOT com
References: <19990301165753 DOT B26464 AT cerebro DOT laendle> <Pine DOT LNX DOT 4 DOT 04 DOT 9903021148300 DOT 1500-100000 AT alcatraz DOT fdf DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.04.9903021148300.1500-100000@alcatraz.fdf.net>; from Dustin Marquess on Tue, Mar 02, 1999 at 11:49:06AM -0600
X-Operating-System: Linux version 2.2.2 (marc AT cerebro) (gcc driver version pgcc-2.93.04 19990131 (gcc2 ss-980929 experimental) executing gcc version 2.7.2.3) 
From: Marc Lehmann <pcg AT goof DOT com>
Reply-To: pgcc AT delorie DOT com

On Tue, Mar 02, 1999 at 11:49:06AM -0600, Dustin Marquess wrote:
> > This is a good idea anyway, since the linux-kernel has a few bugs that
> > keep it from working with the egcs or pgcc snapshots at the moment (maybe
> > even with the releases).
> 
> 	I believe the gcc 2.8.x compat problems in the kernel that
> were causing problems w/ pgcc/egcs were fixed in the late 2.1.x kernel
> series and the 2.2.x kernel series.

Yes, but we now have genuine egcs/pgcc snapshot problems with the kernel,
i.e. changes in the snapshots may break the kernel (different inline
behaviour is the biggest change). No release is affected.

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