Re: [gccsdk] mmap

> 1) OS_DynamicArea returns an error. This could happen if the memory
> request was too big, for example, but seems unlikely.
>
> 2) Only 8 mmap sections at any one time are supported. That includes
> those that malloc may create for large requests, however, malloc
> falls back to its normal allocation routines if there are already
> 8 mmaps. Attempting to create a 9th will result in ENOMEM.
> memalign uses malloc and so will suffer the same limitations.
>
> I usually replace any mmap calls with my own dynamic area memory
> allocator.
>
OK I am not sure , but I belive this is the frist one. Will hunt for others

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK