Date: Tue, 9 Mar 1999 18:11:51 +0100
To: pgcc AT delorie DOT com
Subject: Re: pgcc-2.92.21 internal compiler error
Message-ID: <19990309181151.J2217@cerebro.laendle>
Mail-Followup-To: pgcc AT delorie DOT com
References: <19990301042931 DOT D24507 AT entity DOT netcologne DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: =?iso-8859-1?Q?=3C19990301042931=2ED24507=40entity=2Enetcologne=2Ede=3E?=
 =?iso-8859-1?Q?=3B_from_Johnny_Teve=DFen_on_Mon=2C_Mar_01=2C_1999_at_04:?=
 =?iso-8859-1?Q?29:32AM_+0100?=
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 Mon, Mar 01, 1999 at 04:29:32AM +0100, Johnny Teveßen wrote:
> Hi!
> 
> During compilation of Python-1.5.2b2, the abovementioned pgcc
> stopped with this message:

Thanks for your report, this is indeed a bug in pgcc (or egcs), I'll
investigate. IT might be caused by invalid asm()'s, though.

On which os (and, in case of linux, which libc) did you compile it?


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