Index
> Compiler Internals > [bug ?] FASM memory management, FASM vs FASMD, future develo |
| Author |
|
|
Tomasz Grysztar 31 Dec 2006, 09:01
There are no different approaches, it always tries to allocate all of the available of extended memory and if this failed for some reason, it reduces the request twice and tries again. With FASMD the only difference is that it uses a plenty of fixed-size blocks for editor use.
If there are any problems with this schemma, the -m switch may help. |
|||
31 Dec 2006, 09:01 |
|
|
DOS386 31 Dec 2006, 18:23
Quote: There are no different approaches, it always tries to allocate all of the available of extended memory and if this failed for some reason, it reduces the request twice and tries again. OK, this probably explains the 1/2 ... Quote: With FASMD the only difference is that it uses a plenty of fixed-size blocks for editor use. But can FASMD use the unreal mode ??? For me it cries about no DPMI ... _________________ Bug Nr.: 12345 Title: Hello World program compiles to 100 KB !!! Status: Closed: NOT a Bug |
|||
|
31 Dec 2006, 18:23 |
|
< Last Thread | Next Thread > |
Forum Rules:
|