This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Out of memory errors when not out of memory ... what to do for OSF 4.0
- From: Richard Henderson <rth at redhat dot com>
- To: Gareth Pearce <tilps at hotmail dot com>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 17 Apr 2002 17:38:26 -0700
- Subject: Re: Out of memory errors when not out of memory ... what to do for OSF 4.0
- References: <F177LjDQa3VMeCHECMm00006628@hotmail.com>
On Wed, Apr 17, 2002 at 04:24:00AM +0000, Gareth Pearce wrote:
> The problem is (seems to be) that OSF has system limits predefined at a far
> too low level, for a number of vm parameters. including a maximum of 200
> mem-maps per process.
It's not a problem with too-small ulimit settings?
> (without this change, mmap has to be disabled in autohost.h in order to
> boostrap)
--with-gc=simple
> b) prehaps a small check could be added to configure for OSF/1 alpha to
> display a warning saying that their mmap limit is too low, if it is.
Possibly. You'd have to write such a thing.
r~