This is the mail archive of the libstdc++@sources.redhat.com mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: ctor_copy_dtor test allocates ridiculous amounts of memory

To: Zack Weinberg <zackw at Stanford dot EDU>
Subject: Re: ctor_copy_dtor test allocates ridiculous amounts of memory
From: Richard Henderson <rth at cygnus dot com>
Date: Sat, 7 Oct 2000 14:07:04 -0700
Cc: Benjamin Kosnik <bkoz at redhat dot com>, gcc-bugs at gcc dot gnu dot org, libstdc++ at sources dot redhat dot com
References: <20001007115634.B4717@wolery.stanford.edu> <Pine.SOL.3.91.1001007123028.21237B-100000@taarna.cygnus.com> <20001007130048.A4894@wolery.stanford.edu>

On Sat, Oct 07, 2000 at 01:00:48PM -0700, Zack Weinberg wrote:
> As a rule of thumb, I'd say that all execution tests should consume no
> more than two megabytes of RAM.  Yes, two.  There's still people out
> there with 8 and 16 megabyte systems.

I think I have to agree.  If we want to test bad_alloc, 
then we should _impose_ tiny resource limits first.


r~

References:
- ctor_copy_dtor test allocates ridiculous amounts of memory
  - From: Zack Weinberg
- Re: ctor_copy_dtor test allocates ridiculous amounts of memory
  - From: Benjamin Kosnik
- Re: ctor_copy_dtor test allocates ridiculous amounts of memory
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]