From owner-freebsd-current Tue Sep 15 01:51:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22871 for freebsd-current-outgoing; Tue, 15 Sep 1998 01:51:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hen.scotland.net (hen6.scotland.net [194.247.64.6] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22851 for ; Tue, 15 Sep 1998 01:51:27 -0700 (PDT) (envelope-from freebsd@timog.prestel.co.uk) Received: from e2c6p46.scotland.net ([148.176.237.110] helo=timog.prestel.co.uk) by hen.scotland.net with esmtp (Exim 1.90 #5) for current@freebsd.org id 0zIqo3-0007K0-00; Tue, 15 Sep 1998 09:49:52 +0100 Received: (qmail 220 invoked by uid 1002); 15 Sep 1998 08:35:07 -0000 Message-ID: <19980915093507.A204@prestel.co.uk> Date: Tue, 15 Sep 1998 09:35:07 +0100 From: Timo Geusch To: current@FreeBSD.ORG Subject: gcc-2.7.2.1 internal compiler error Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, 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? Although I am quite an accomplished C/C++ programmer I always feel lost when looking at the gcc parsers, so I'm afraid I can't be much help in fixing the problem. Anyway, if it makes sense to open a pr, I will do so (oh yeah, it *will* include the code that triggers the error :). Cheers, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message