X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Thu, 07 Feb 2002 22:00:20 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	sandmann AT clio DOT rice DOT edu
Message-Id:	<1676-Thu07Feb2002220020+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com, ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De,
	pavenis AT lanet DOT lv
In-reply-to:	<10202071825.AA14352@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: conflicting types for bzero (gcc303)
References:	<10202071825 DOT AA14352 AT clio DOT rice DOT edu>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Thu, 7 Feb 2002 12:25:19 -0600 (CST)
> 
> A quick test of Andris's suggestion (in a GNUC 3 ifdef) :
> #define bzero(s,n) __builtin_bzero(s,n)
> 
> Also seemed to work fine (even with -fno-builtin)
> 
> Note that if we make this change we always use the builtin with
> GCC 3.x; if we don't we always seem to generate code for our libc 
> bzero (backward compatible but gives occasional warning).
> 
> So a simple string.h ifdef for __GNUC__ >=3 to use the above
> instead of our prototype would fix the warning - and upgrade
> you to posix behavior using GCC 3.x.  While this would still
> break anyone trying to use a return argument, they probably need
> to make other code changes for GCC 3.x anyway, or could use 2.x.

I'd suggest to make this change: a partial solution is better than no
solution.

- Raw text -