From: "Pedro Lamarão" <pedro.lamarao@ccppbrasil.org>
To: gcc@gcc.gnu.org
Subject: Re: [gcc-in-cxx] replacing qsort with std::sort
Date: Sun, 30 Aug 2009 10:37:00 -0000 [thread overview]
Message-ID: <15727b460908291549t1c87c6bbi57d20b1539360f9a@mail.gmail.com> (raw)
In-Reply-To: <1251532218.3790.10.camel@sara.home>
2009/8/29 Magnus Fromreide <magfr@lysator.liu.se>:
>
> Why the changes to gcc/system.h where you unpoision malloc and realloc?
> Why the changes to libcpp/system.h where you unpoision malloc, realloc,
> calloc and strdup?
Including <algorithm> requires them for some reason.
I haven't really looked into it.
--
P.
next prev parent reply other threads:[~2009-08-29 22:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 9:59 Pedro Lamarão
2009-08-12 13:12 ` Richard Guenther
2009-08-12 14:33 ` Pedro Lamarão
2009-08-12 13:21 ` Ian Lance Taylor
2009-08-29 11:26 ` Pedro Lamarão
2009-08-29 19:42 ` Magnus Fromreide
2009-08-30 10:37 ` Pedro Lamarão [this message]
2009-08-31 16:10 ` Richard Henderson
2009-08-31 16:18 ` Pedro Lamarão
2009-08-31 18:36 ` Richard Henderson
2009-08-31 18:54 ` Richard Guenther
2009-08-31 19:01 ` Richard Henderson
2009-08-31 19:06 ` Pedro Lamarão
2009-09-02 0:24 ` Michael Matz
2009-09-02 12:57 ` Pedro Lamarão
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15727b460908291549t1c87c6bbi57d20b1539360f9a@mail.gmail.com \
--to=pedro.lamarao@ccppbrasil.org \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).