From owner-freebsd-current Wed Apr 10 2:19:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 789C637B419 for ; Wed, 10 Apr 2002 02:19:04 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA10497; Wed, 10 Apr 2002 19:18:55 +1000 Date: Wed, 10 Apr 2002 19:19:05 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: libkern/quad.h In-Reply-To: <200204091458.g39Ewg1T000574@Magelan.Leidinger.net> Message-ID: <20020410191448.V7317-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Tue, 9 Apr 2002, Alexander Leidinger wrote: > quad.h contains: > ---snip--- > /* > * XXX > * Compensate for gcc 1 vs gcc 2. Gcc 1 defines ?sh?di3's second argument > * as u_quad_t, while gcc 2 correctly uses int. Unfortunately, we still use > * both compilers. > */ > #if __GNUC__ >= 2 > typedef unsigned int qshift_t; > #else > typedef u_quad_t qshift_t; > #endif > ---snip--- > > Is this still valid? Does someone really use gcc 1 to compile FreeBSD? This became invalid before FreeBSD-2.0 was released. Most special cases to support gcc's before approx 2.7 are now bogus. Unlike the above, most of them are just for optimizations or for better diagnostics, so removing them shouldn't break compiling with old versions of gcc any more than not having the for other C compilers breaks compiling with other C compilers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message