From owner-freebsd-current Fri Nov 22 4: 4:47 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 21EAE37B401 for ; Fri, 22 Nov 2002 04:04:46 -0800 (PST) Received: from popelschnipser.de (ultrakoreggd.org [217.160.78.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E6EC43E91 for ; Fri, 22 Nov 2002 04:04:44 -0800 (PST) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 15074 invoked by uid 1048); 22 Nov 2002 12:04:43 -0000 Received: from marc@informatik.uni-bremen.de by p10089345 by uid 1045 with qmail-scanner-1.15 (clamscan: 0.54. spamassassin: 2.42. Clear:. Processed in 0.495336 secs); 22 Nov 2002 12:04:43 -0000 Received: from unknown (HELO ?192.168.100.100?) (217.82.114.46) by ultrakoreggd.org with SMTP; 22 Nov 2002 12:04:42 -0000 Date: Fri, 22 Nov 2002 13:04:40 +0100 From: Marc Recht To: Terry Lambert , Steve Kargl Cc: Harald Arnesen , David Schultz , David O'Brien , freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.2.1 release import? Message-ID: <23160000.1037966680@leeloo.intern.geht.de> In-Reply-To: <3DDE1711.6B9606B4@mindspring.com> References: <55350000.1037811461@leeloo.intern.geht.de> <20021121041449.GA17530@dragon.nuxi.com> <20021121214614.GA6062@HAL9000.homeunix.com> <87bs4iczjd.fsf@basilikum.skogtun.org> <87590000.1037924015@leeloo.intern.geht.de> <3DDD7F10.BFED05F7@mindspring.com> <120820000.1037929067@leeloo.intern.geht.de> <3DDDCD32.6D74D775@mindspring.com> <20021122064625.GA12620@troutmask.apl.washington.edu> <3DDE1711.6B9606B4@mindspring.com> X-Mailer: Mulberry/3.0.0a5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 > What does it do for all the other code in -ports, and in the > comp.source.* archives, and that anyone else has ever written, > such that you know it doesn't cause more problems than it > solves? I don't think that the system cc is supposed to compile all code ever written. IMHO It should compile the system (and the port versions of gcc) - not more not less. > Supposedly, bringing in 3.2 was going to solve more problems > than it caused. It turns out the 4.x compiler, GCC 2.95.3, > also does not have an ICE as a result of compiling that code. The problem with the ports is mostly badly written C++ code. Since most (all?) Linux distributions are using gcc 3.2.x by now I'm quite sure it will be fixed over the time.. > When you are updating tools, it's actually about risk/reward; > the risk of not supporting IA64, and the risk of the object > file compatability has (supposedly) be addressed. The question is, how big is the Step from a Nov. pre-release to the release version of gcc 3.2.1. > The only other reasonable path would be to tie FreeBSD releases > to GCC releases, plus some period of time for burn-in, and that > really isn't reasonable: 3.3 was supposed to be out already; > should FreeBSD's release schedule slip every time GGC's slips? IMHO it would be a big mistake to tie FreeBSD releases to GCC releases. And going for the latest and greatest isn't an option, too. This time it could just "fit". I'm wondering if I should mention the new binutils.. :) Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message