From owner-freebsd-current Sun Sep 1 11:58: 3 2002 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 0C61A37B400; Sun, 1 Sep 2002 11:57:56 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [204.179.120.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF2143E6A; Sun, 1 Sep 2002 11:57:54 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from smtp-relay01.mac.com (smtp-relay01-en1 [10.13.10.224]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id g81IvsmF009012; Sun, 1 Sep 2002 11:57:54 -0700 (PDT) Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66]) by smtp-relay01.mac.com (8.12.1/8.12.1/1.0) with ESMTP id g81IvsVw027633; Sun, 1 Sep 2002 11:57:54 -0700 (PDT) Received: from David-Leimbachs-Computer.local ([67.32.249.192]) by asmtp02.mac.com (Netscape Messaging Server 4.15) with ESMTP id H1RWOH00.76Y; Sun, 1 Sep 2002 11:57:53 -0700 Date: Sun, 1 Sep 2002 13:57:52 -0500 Subject: Re: gcc 3.1 / streambuf.h broken with "using namespace std;" Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) Cc: Terry Lambert , freebsd-current@FreeBSD.ORG, Alexander Langer , Gerald Pfeifer To: obrien@FreeBSD.ORG From: leimy2k@mac.com In-Reply-To: <20020901183043.GF94999@dragon.nuxi.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.543) 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 > > It is *that* simple. > yep. > Rather than bitch that 3.1.1 "sucks"; we should thanking the GCC > Steering > Committee that after much thought they were willing to take the > vendors' > needs into account. I am not sure FreeBSD would have done the same. > I never said it sucked... I think the ABI standardization process is *very* important as it will be an enabling technology... these things don't come without some growing pains. > >> Actually they have been trying to make this work all along and is >> probably why they break ABI compatibility. 3.1 has issues with >> template classes that use functions containing static variables [at >> least a pre-release of it did on Darwin/OS X]. > > Apple highly modifies the GCC sources. So any bugs/problems/issues you > find in their compiler you cannot blame on the GCC developers w/o > researching the bug/problem/issue. > Wasn't aware to what degree GCC is modified by Apple... I knew they did some things... > >> 3.2 necessary for some people [though I hope every time the fix >> something that their test-cases increases by one.... that would be >> smart anyway]. > > The test suite does. We should be so lucky to have such a test suite. Indeed! :) > >> 3.2 is the "more confident" ABI and while there are no guarantees that >> 3.3 will work with 3.2... there seems to be better feelings about it. > > Correct. Not only "better feelings" but "fully intended". But as we > saw > with 3.1.0, bugs happen. > Yes... I think you and I are generally on the same page :). > > >>> It was my understanding that FreeBSD 5.0 release was not going >>> to be GCC 3.3 (because GCC 3.3 would not be released in time for >>> FreeBSD to not be "pulling a RedHat" if they shipped a beta and >>> called it 3.3) , might be GCC 3.2, and was currently down-rev >>> from there. > > 3.3.0 will be released before FreeBSD 5.1. It is my advice to > FreeBSD'ville that we go with a GCC 3.3 snapshot for FBSD 5.0 and a GCC > 3.3.0 release for FBSD 5.1. That way we can get the new features of > 3.3 > into our 5.x branch. AND get bug fixes by importing 3.3.1 and 3.3.2 > into > later FBSD 5.x releases. > Yes! yes! YES! :) 100% agree! IMO DP-2 should have gcc-3.3 snap perhaps even FreeBSD 5.0 release [assuming that 5.0 is released on November 20, 2002... I have doubts but I'd rather it be done properly than done quickly... Its one reason I like FreeBSD and the community.] Seems like things are going exactly as they should... going to 3.3 should greatly decrease developer pain overall. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message