From owner-freebsd-current Tue Sep 15 23:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07452 for freebsd-current-outgoing; Tue, 15 Sep 1998 23:03:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hen.scotland.net (hen.scotland.net [194.247.65.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07443 for ; Tue, 15 Sep 1998 23:03:41 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e2c6p44.scotland.net ([148.176.237.108] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for current@freebsd.org id 0zJAfD-000210-00; Wed, 16 Sep 1998 07:02:04 +0100 Received: (qmail 619 invoked by uid 1002); 15 Sep 1998 21:44:39 -0000 Message-ID: <19980915224438.A581@prestel.co.uk> Date: Tue, 15 Sep 1998 22:44:38 +0100 From: Timo Geusch To: current@FreeBSD.ORG Subject: Re: gcc-2.7.2.1 internal compiler error References: <19980915093507.A204@prestel.co.uk> <199809151727.KAA21703@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199809151727.KAA21703@austin.polstra.com>; from John Polstra on Tue, Sep 15, 1998 at 10:27:35AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 15, 1998 at 10:27:35AM -0700, John Polstra wrote: > > I'd need some opinions on how to deal with an internal compiler error in g++ > > (stock 2.7.2.1 in -current as of 14/9). I've got a small piece of C++ code > > which triggers an internal compiler error. In the light of the recent > > discussion on possibly moving to gcc 2.8.1 (which does NOT exhibit this > > behaviour), does it still make sense to open a PR on it? > > It would most likely be a waste of time. You'll have better luck > filing g++ bug reports with the GNU folks. First, you should try > gcc-2.8.1 and see if the same problem exists in that version. If it > does, go ahead and report the bug to the FSF. If it doesn't, then > start using gcc-2.8.1. So I thought. I was actually using 2.8.1 to make sure that I didn't trigger that error using some invalid code; Code was as perfectly valid as expected, but 2.7.2.1 turned out to be less than perfect. Oh well. Workaround is known anyway. Thanks, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message