This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch: malloc function attribute
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Patch: malloc function attribute
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 30 Nov 1999 00:12:47 -0700
- cc: gcc-patches at gcc dot gnu dot org, green at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199911291348.IAA21925@caip.rutgers.edu>you write:
> > From: Jeffrey A Law <law@cygnus.com>
> >
> > I believe xrealloc is safe. Consider the conditions under which is
> > can return the same pointer, I believe all are safe.
>
> Okay, I'll tag xrealloc, but not spaces.
Note it may be the case that xrealloc/realloc are not safe. It depends on
what the standard has to say about Mark's example. So you might want to hold
off marking xrealloc.
> > > list. (BTW, what the heck is spaces good for anyway?)
> > No idea. Who added it?
>
> Thu Oct 24 02:29:26 1991 Fred Fish (fnf at cygnus.com)
>
> * [...] spaces.c: New files containing either portable C
> versions or emulations using native library calls.
>
> Its been a few years. :-) Does Fred still work for Cygnus?
He still works for us as a contractor. You can certainly still reach him via
fnf@cygnus.com.
> IMHO, I don't think we need to handle it. This case will only issue a
> warning, not a hard error. E.g. consider:
OK. Good enough.
jeff