Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.arch
Subject: Re: 80286 protected mode
Date: Thu, 17 Oct 2024 03:16:13 -0700
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <86ttdbvxua.fsf@linuxsc.com>
References: <2024Oct8.092821@mips.complang.tuwien.ac.at> <ve5ek3$2jamt$1@dont-email.me> <be506ccef76d682d13205c69c761a086@www.novabbs.org> <ve6oiq$2pag3$1@dont-email.me> <ve6tv7$2q6d5$1@dont-email.me> <86y12uy8ku.fsf@linuxsc.com> <jwv34kx5afd.fsf-monnier+comp.arch@gnu.org> <3f2cb127c8d5dc2381fc80631a495e3e@www.novabbs.org> <8HBPO.471560$_o_3.464389@fx17.iad> <d8cffb389b3fd055ee70e87da9a3403a@www.novabbs.org> <b6RPO.380391$FzW1.307451@fx14.iad> <rhq0hj5h9nfd9qbb64mc8jvaf8bonf61q9@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Thu, 17 Oct 2024 12:16:14 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="4d902cc0473bdb0fc4a91596ca166507";
	logging-data="2853073"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18beN0uZ+T8Naj7Q/UlAIo620WypD499Lk="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:oXld3UZnc3d3k9Z40Ylvg7vkVE8=
	sha1:Hzq6mh1mEt4hnAyHrun/OpHpx3I=
Bytes: 2344

George Neuner <gneuner2@comcast.net> writes:

> On Wed, 16 Oct 2024 15:38:47 GMT, scott@slp53.sl.home (Scott Lurndal)
> wrote:
>
>> mitchalsup@aol.com (MitchAlsup1) writes:
>>
>>> On Tue, 15 Oct 2024 22:05:56 +0000, Scott Lurndal wrote:
>>>
>>>> mitchalsup@aol.com (MitchAlsup1) writes:

[...]

>>>>> malloc() used to be standard K&R C--what dropped it from the
>>>>> standard ??
>>>>
>>>> It still is part of the ISO C standard.
>>>
>>> The paragraaph with 3 >'s indicates malloc() cannot be written in
>>> standard C.  It used to be written in standard K&R C.
>>
>> K&R may have been 'de facto' standard C, but not 'de jure'.
>>
>> Unix V6 malloc used the 'brk' system call to allocate space
>> for the heap.   Later versions used 'sbrk'.
>>
>> Those are both kernel system calls.
>
> Yes, but malloc() subdivides an already provided space.

Not necessarily.

> Because that space can be treated as a single array of char,

Not always.