From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 12:23:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3F816A4CE for ; Fri, 30 Jul 2004 12:23:22 +0000 (GMT) Received: from dignus.com (client196-2.dsl.intrex.net [209.42.196.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3788743D39 for ; Fri, 30 Jul 2004 12:23:19 +0000 (GMT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.12.9p2/8.12.9) with ESMTP id i6UCMTHw028016; Fri, 30 Jul 2004 08:22:33 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.11.6/8.11.3) id i6UCMVr13060; Fri, 30 Jul 2004 08:22:31 -0400 (EDT) (envelope-from rivers) Date: Fri, 30 Jul 2004 08:22:31 -0400 (EDT) From: Thomas David Rivers Message-Id: <200407301222.i6UCMVr13060@lakes.dignus.com> To: geoff@sea-incorporated.com, pdseniura@techie.com In-Reply-To: <20040729175604.GA95628@caribbean.sea-incorporated.com> X-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,IN_REP_TO,QUOTED_EMAIL_TEXT version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-current@freebsd.org Subject: Re: about the gcc 3.4.x problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 12:23:22 -0000 "Geoffrey C. Speicher" > > GCC-3.4 is in the tree; rejoice and be glad. GCC-3.5 is not even an > issue. Just because Apple is using it doesn't mean everybody should. > Apple has the resources to adopt gcc prereleases early, and thoroughly > test and fix all the problems that they will undoubtedly find. > On a side note - I'm not sure Apple has/had those resources. We reported a bug in their gcc (it wouldn't compile some of our sources, complaining of an internal error) in OS X 10.1. (A pre-release of GCC 3.2.x, I think.) The problem was fixed, about a year later, when the latest OS X was released... so, at last, our products are available on a mac. We never received a fix and had to buy the new release to get the new versions. Many e-mails went to Apple asking about the status of the problem, pointing to where the fix needed to be made, etc... but - nothing _ever_ came back from Apple... and then, a couple of days before the latest release, the bug was simply closed. So - it seems, they didn't, in our case, have the resources to test and correct problems. I have the opinion they simply jump on the latest... this is admittedly anecdotal. And, might simply be the exception that proves the rule :-) - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com