This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Built-in bzero in GCC 3.0.2
- To: ghazi at caip dot rutgers dot edu
- Subject: Re: Built-in bzero in GCC 3.0.2
- From: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Date: Mon, 5 Nov 2001 10:46:28 +0200 (IST)
- CC: gcc at gcc dot gnu dot org
- References: <200111050531.AAA17032@caip.rutgers.edu>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Mon, 5 Nov 2001 00:31:02 -0500 (EST)
> From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
>
> void bzero();
>
> Note the return type is "void", not "void *". See:
> http://www.opengroup.org/onlinepubs/007908799/xsh/bzero.html
Right. The development sources already changed to this standard
specification. But it will take time before the next release of the
library is out.
> Are your headers standard DJGPP of the latest release?
Yes, I use the standard headers as shipped with the latest official
release.
> If so and if we want to support it, we might silently elide nonansi
> builtins whose return type doesn't match. Not sure if this is
> preferred or not.
What, if any, are other options?
My goal is quite limited: I'd like to let users compile GDB without
seeing warnings. If there's a GCC option I could use to avoid the
warning, it'd be fine, provided that this option will not cause older
versions of the compiler (say, the 2.95.x series at least) to barf.
Failing that, your suggestion sounds fine. Thanks.