Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: The different groups and segments of object files Date: Fri, 26 Jun 2020 00:09:35 +0200 Organization: Compilers Central Lines: 20 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <20-06-024@comp.compilers> References: <20-06-004@comp.compilers> <20-06-005@comp.compilers> <20-06-023@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com In-Reply-To: <20-06-023@comp.compilers> Xref: csiph.com comp.compilers:2545 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]