This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/8230: Buggy allocator behaviour
- From: Richard Henderson <rth at redhat dot com>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Matt Austern <austern at apple dot com>, Benjamin Kosnik <bkoz at redhat dot com>, bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, jkanze at caicheuvreux dot com, gcc-gnats at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Fri, 15 Nov 2002 14:41:38 -0800
- Subject: Re: libstdc++/8230: Buggy allocator behaviour
- References: <F21E0F03-F81D-11D6-B4E9-00039390D9E0@apple.com> <m34rajokhm.fsf@soliton.integrable-solutions.net>
On Thu, Nov 14, 2002 at 11:27:17PM +0100, Gabriel Dos Reis wrote:
> Maybe RTH could provide us with some datapoint here?
"It depends".
> | Second, if the answer to question 1 is "a lot": is there some sensible
> | way to use this in the compiler itself? I suppose it'd have to involve
> | some ghastly macro hackery because of the bootstrap problem, but
> | it we're talking big performance wins, it might be worth it.
>
> If the answer to the first question is "a lot", then I agree with you
> that it makes perfect sense to use it in the compiler itself. I
> could imagine something along the lines
>
> #if !defined(__GNUC__) || __GNUC__ < 3 /* correct the version number */
> # define __builtin_expect(EXP, PROB) EXP
> #endif
>
> in system.h or wherever appropriate.
I don't think it's worth it, except _possibly_ in the
ENABLE_CHECKING macros.
r~