From owner-freebsd-current Sat Jun 22 4:56: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id 4FD4A37B401 for ; Sat, 22 Jun 2002 04:55:30 -0700 (PDT) Received: from fwd04.sul.t-online.de by mailout05.sul.t-online.com with smtp id 17LjUB-0007EQ-06; Sat, 22 Jun 2002 13:55:23 +0200 Received: from Gatekeeper.FreeBSD.org (520047440004-0001@[217.81.3.84]) by fmrl04.sul.t-online.com with esmtp id 17LjU7-1Pw4gaC; Sat, 22 Jun 2002 13:55:19 +0200 Received: from StefanEsser.FreeBSD.org (StefanEsser [10.0.0.1]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 67D9A63B3; Sat, 22 Jun 2002 13:55:19 +0200 (CEST) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 5B6BA1EFF; Fri, 21 Jun 2002 20:08:39 +0200 (CEST) Date: Fri, 21 Jun 2002 20:08:39 +0200 From: Stefan Esser To: Martin Blapp Cc: Kris Kennaway , Yamada Ken Takeshi , freebsd-current@freebsd.org Subject: Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries Message-ID: <20020621180839.GA608@StefanEsser.FreeBSD.org> Reply-To: Stefan Esser References: <20020621154758.F550-100000@levais.imp.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020621154758.F550-100000@levais.imp.ch> User-Agent: Mutt/1.5.1i X-Sender: 520047440004-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-06-21 16:35 +0200, Martin Blapp wrote: > I still wonder why we make workarounds like this if one could just > use /usr/local/bin/gcc31 to have it fixed. Sorry, but the compiler bug has been present in the port version of GCC-3.1 as well, a few weeks ago, and existed in the version to become GCC-3.1.1 ... I opened a PR at gcc.org, didn't get any feedback, yet. > Why mess around with a buggy compiler if a working one is around ? Only a single source file triggers the optimizer bug, and the work-around should be appropriate until the compiler is fixed, IMHO. > Why don't we update the pre 3.1 gcc in CURRENT to a working one ? I'm sure that there is a lot of work being done to keep up with the latest gcc versions. It just isn't that simple to upgrade such a crucial build tool (if compiling a new gcc fails, then make world doesn't have much of a chance of succeeding ...) > Yes, I turned on -O and O2 again ;-) Did the GCC-3.1 from ports compile translate.c with optimization turned on ??? It didn't, just one or two weeks ago. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message