This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Speeing up __cxa_atexit
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 06 Jun 2002 21:53:34 -0700
- Subject: Re: Speeing up __cxa_atexit
--On Thursday, June 06, 2002 08:02:38 PM +0200 Gabriel Dos Reis
<gdr@codesourcery.com> wrote:
Mark Mitchell <mark@codesourcery.com> writes:
[...]
| See my point about what happens if users replace functions like malloc.
Certainly I don't undertand what is really going on, but I'm sure when
the user replaces malloc(), he/she invokes undefined behaviour.
Very well.
In practice, from a QOI point of view, we should try to support people
replacing various C library functions, but I am happy to believe that
they are not allowed to do so.
Using "operator new" instead of "malloc" in my argument is fine.
Thanks for pointing this out,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com