This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Projects for beginners
- To: jsm28 at cam dot ac dot uk, zackw at Stanford dot EDU
- Subject: Re: Projects for beginners
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Wed, 31 Jan 2001 08:48:58 -0500 (EST)
- Cc: gcc at gcc dot gnu dot org
> - Get rid of all remaining uses of bcopy (requires understanding
> the code well enough to tell whether they should be memcpy or
> memmove).
>
> - Then apply #pragma GCC poison to bcmp/bzero/bcopy/rindex
> <URL:http://gcc.gnu.org/ml/gcc-patches/2000-11/msg00432.html>
I'd like to poison malloc/realloc/calloc/strdup too and enforce using
the "x" versions from libiberty. But two or three legit uses still
occur. Is there a way to say use malloc even though its poisoned?
Perhaps instead we could #define malloc() to #error and make the legit
uses call (malloc)() which bypasses the macro?
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions