From owner-freebsd-current Wed Dec 29 19:19: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7025115123 for ; Wed, 29 Dec 1999 19:19:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA14398; Wed, 29 Dec 1999 19:18:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA16312; Wed, 29 Dec 1999 19:18:59 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 19:18:59 -0800 From: "David O'Brien" To: Amancio Hasty Cc: current@FreeBSD.org Subject: Re: gcc compile error Message-ID: <19991229191859.Q2130@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991229185808.C16090@dragon.nuxi.com> <199912300303.TAA46481@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912300303.TAA46481@rah.star-gate.com>; from hasty@rah.star-gate.com on Wed, Dec 29, 1999 at 07:03:47PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 3. Raise this issue with Cygnus. > > Not really Cygnus is the wrong organization to raise this issue . Could you *please* explain why??? Gcc 2.96 will not be out before 4.0. So Gcc 2.95.x is what is going into 4.0. Now should a Gcc 2.95.3 were to come out, then we'd get a new compiler for 4.0. > As someone else pointed out the gcc-devel port does not exhibit the bug > which I posted. Lets think about this in FreeBSD terms -- 4.0 does not have some problem that 3.4-R does. However it wasn't known that 3.4-R had this problem and the reason why 4.0 does not have this problem is due to *tons* of code changes, not necessarily in response to this problem. Now would the FreeBSD Project like to know that there is a problem with 3.4-R that isn't in 4.0 along with a test case to show the problem? Would the FreeBSD Project, maybe just maybe be interested in fixing the problem and releasing a 3.5-R? Just like FreeBSD, EGCS has two code branches. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message