This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: C++ PATCH: operator delete[]
- To: Nathan Sidwell <sidwell at codesourcery dot com>
- Subject: Re: C++ PATCH: operator delete[]
- From: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Date: 02 Feb 2000 09:10:26 -0200
- Cc: Nathan Sidwell <nathan at acm dot org>, gcc-patches at gcc dot gnu dot org, James Kanze <f981500 at FFZJ0LX0 dot bank dot dresdner dot net>
- References: <3891A0B6.1C1BC584@acm.org> <or3drfgiwd.fsf@garnize.lsd.ic.unicamp.br> <3896C6BB.3B23E19C@acm.org> <orpuuguwv2.fsf@garnize.lsd.ic.unicamp.br> <38980DC0.F755298B@codesourcery.com>
On Feb 2, 2000, Nathan Sidwell <sidwell@codesourcery.com> wrote:
> I just don't like this idea of the delete instruction sequence being
> a sequence of calls to functions which all start
> bz ptr,exit
> call lower_level_delete
> exit: return
> (even with tail call optimization this is still two jumps in a row).
> Yeah, micro optimization and all that, sorry :-)
Yup, I agree with the point about optimization. But my reading of the
Standard says we should do it the way my patch goes. But your reading
about the implied `at minimum' also makes sense.
> I'll be quiet now.
Ditto.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them