From owner-freebsd-current Tue Sep 15 10:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19932 for freebsd-current-outgoing; Tue, 15 Sep 1998 10:28:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19905 for ; Tue, 15 Sep 1998 10:28:00 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id KAA21703; Tue, 15 Sep 1998 10:27:35 -0700 (PDT) (envelope-from jdp) Message-Id: <199809151727.KAA21703@austin.polstra.com> To: freebsd@timog.prestel.co.uk Subject: Re: gcc-2.7.2.1 internal compiler error In-Reply-To: <19980915093507.A204@prestel.co.uk> References: <19980915093507.A204@prestel.co.uk> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 15 Sep 1998 10:27:35 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980915093507.A204@prestel.co.uk>, Timo Geusch 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. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message