Re: The different groups and segments of object files

Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Fri, 26 Jun 2020 00:09:35 +0200

          From comp.compilers
Related articles
[2 earlier articles]
Re: The different groups and segments of object files DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-06-20)
Re: The different groups and segments of object files gah4@u.washington.edu (2020-06-21)
Re: The different groups and segments of object files johann@myrkraverk.invalid (Johann 'Myrkraverk' Oskarsson) (2020-06-25)
Re: The different groups and segments of object files johann@myrkraverk.invalid (Johann 'Myrkraverk' Oskarsson) (2020-06-25)
Re: The different groups and segments of object files DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-06-25)
Re: The different groups and segments of object files DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-06-25)
Re: The different groups and segments of object files DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-06-26)
Re: The different groups and segments of object files gah4@u.washington.edu (2020-07-02)
| List of all articles for this month |
From: Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Newsgroups: comp.compilers
Date: Fri, 26 Jun 2020 00:09:35 +0200
Organization: Compilers Central
References: 20-06-004 20-06-005 20-06-023
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="88301"; mail-complaints-to="abuse@iecc.com"
Keywords: code, history, comment
Posted-Date: 25 Jun 2020 20:15:04 EDT
In-Reply-To: 20-06-023

Am 25.06.2020 um 22:40 schrieb Hans-Peter Diettrich:


> AFAIR the starting
> segment selector allowed to access at least 512 MB (8 consecutive
> segments). This feature did not allow to break the 4GB total limit, but
> it allowed for contiguous data areas bigger than 64KB.
>
> DoDi
> [Nobody I knew used huge model because it was so very very slow. There
> was no way on 16-bit x86 to access more than 64K at a time without runtime
> segment calculations. -John]


The 16/32 bit address size prefix inverts the default address size, i.e.
allows to use 32 bit addresses and offset registers with 16 bit code.


I used 32 bit offsets in 16 bit code with the Borland compilers,
disassembled the generated machine code. I never used the HUGE model.


DoDi
[Oh, running on a 386, sure, that would have worked. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.