Date: Tue, 15 Sep 1998 22:44:38 +0100 From: Timo Geusch <freebsd@timog.prestel.co.uk> To: current@FreeBSD.ORG Subject: Re: gcc-2.7.2.1 internal compiler error Message-ID: <19980915224438.A581@prestel.co.uk> In-Reply-To: <199809151727.KAA21703@austin.polstra.com>; from John Polstra on Tue, Sep 15, 1998 at 10:27:35AM -0700 References: <19980915093507.A204@prestel.co.uk> <199809151727.KAA21703@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980915224438.A581>