This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: hash policy patch
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: François Dumont <frs dot dumont at gmail dot com>
- Cc: Paolo Carlini <pcarlini at gmail dot com>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 31 Aug 2011 11:54:57 +0200
- Subject: Re: hash policy patch
- References: <4E2F1A56.3010000@free.fr> <4E2F204B.6060207@oracle.com> <4E31C6CE.2070906@free.fr> <7B3982F6-FEAA-4023-AC36-84B10A513651@oracle.com> <4E3849E9.5000505@free.fr> <4E4E373C.70408@oracle.com> <4E5D45A9.5040606@gmail.com> <4E5E0162.8050702@oracle.com>
On 08/31/2011 11:39 AM, Paolo Carlini wrote:
I can try to run the patch + testcases with the -D_GLIBCXX_RES_LIMITS
removed,
Can't possibly change anything on Linux. Because the macro is defined
anyway if memory limit testing is supported by the target, just see
testsuite_hooks.cc. Actually, that's why in any case we want at least:
us.max_load_factor(0.001);
#ifdef _GLIBCXX_RES_LIMITS
VERIFY( false && "Max load factor modification hasn't generated an"\
" exception" );
#endif
Paolo.