huge memory model (Announce)
> Indeed no. Turbo C supported huge pointers allowing to allocate blocks
> larger than 64K.
>
> https://www.vogons.org/viewtopic.php?t=51678
That seems to require manually defining the
pointers as huge, which is not what I expect
to have to do when I pass "-mh" to the
compiler, and in fact, not what I have to do
when I use Watcom.
Watcom is doing exactly what I want.
Someone else with experience with programming
using huge memory model said that it only adds
a few percent overhead to runtime.
In my case, an OS, it shouldn't even be that,
because the computer should be bottlenecked in
the app, not the OS. And the app can be in any
memory model.
BFN. Paul.
Complete thread:
- huge memory model - kerravon, 22.11.2022, 16:30 (Announce)
- huge memory model - Guti, 25.11.2022, 10:23
- huge memory model - kerravon, 25.11.2022, 19:41
- huge memory model - Guti, 29.11.2022, 06:55
- huge memory model - kerravon, 29.11.2022, 08:44
- huge memory model - Guti, 29.11.2022, 06:55
- huge memory model - kerravon, 25.11.2022, 19:41
- huge memory model - Guti, 25.11.2022, 10:23