X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10202062058.AA24120@clio.rice.edu>
Subject: Re: conflicting types for bzero (gcc303)
To: eliz AT is DOT elta DOT co DOT il
Date: Wed, 6 Feb 2002 14:58:16 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com, ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De
In-Reply-To: <3069-Wed06Feb2002221302+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Feb 06, 2002 10:13:03 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

> I think we should modify bzero and bcopy so that they fit the
> (universally accepted) prototypes GCC expects.

This is what was done in CVS - and I agree it is the preferable
thing to do for a new release - where we can document a change
in the binary interface.  There is a small possibility that 
someone is using the return argument today - and I don't think
breaking it in a "refresh" is the right thing.  This is just
a warning - and only with a new compiler.

In addition, I don't believe anyone has the time and energy right 
now to try to rebuild libc/binaries/re-test changes to a v2.03 refresh 
- I was hoping for a quick and easy distribution fix (which might
go in with the djtypes.h fix).

I'd prefer to start a discussion on what remaining features we
want to stuff into 2.04 and when to freeze it/beta it/release it.
(than to spend a big effort refreshing the 2.03 binaries again).

Our allowable time is limited - lets put it to the best use.  If
we can make the warning go away easily, OK - if not, forget it.