From: Nemo Nusquam <cym224@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Memory management in Dennis Ritchie's C Compiler
Date: Mon, 17 Aug 2020 19:06:56 -0400 [thread overview]
Message-ID: <107719ce-b631-c4c9-fedd-ac8845d01213@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2008180839350.825@aneurin.horsfall.org>
On 08/17/20 18:47, Dave Horsfall wrote:
> On Mon, 17 Aug 2020, Dibyendu Majumdar wrote:
>
>> From Wikipedia:
>> sbrk and brk are considered legacy even by 1997 standards (Single UNIX
>> Specification v2 or POSIX.1-1998).[5] They were removed in
>> POSIX.1-2001.[6]
>
> On a whim, I checked a couple of boxes around here (I haven't used sbrk()
> since malloc() came along):
>
> Mac:
>
> The brk and sbrk functions are historical curiosities left over
> from ear-
> lier days before the advent of virtual memory management.
>
> FreeBSD:
>
> The brk() and sbrk() functions are legacy interfaces from before the
> advent of modern virtual memory management.
>
> Both of them come right after the DESCRIPTION header.
More whimsy from "man sbrk" on Solaris 10:
The use of mmap(2) is now preferred because it can be used
portably with all other memory allocation functions and with
any function that uses other allocation functions.
N.
>
> -- Dave
next prev parent reply other threads:[~2020-08-17 23:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 21:50 Dibyendu Majumdar
2020-08-16 15:20 ` arnold
2020-08-16 15:27 ` Jim Geist
2020-08-17 16:13 ` Dan Cross
2020-08-17 20:16 ` Dibyendu Majumdar
2020-08-17 20:34 ` Paul Winalski
2020-08-17 20:43 ` Dibyendu Majumdar
2020-08-17 21:05 ` Warner Losh
2020-08-17 22:47 ` Dave Horsfall
2020-08-17 23:06 ` Nemo Nusquam [this message]
2020-08-17 21:29 ` Dibyendu Majumdar
2020-08-24 15:58 ` Dan Cross
2020-08-24 17:08 ` John Cowan
2020-08-24 17:15 ` Clem Cole
2020-08-24 17:24 ` Clem Cole
2020-08-24 17:20 ` Dan Cross
2020-08-25 23:06 ` Arthur Krewat
2020-08-17 2:02 Noel Chiappa
2020-08-17 18:02 ` Paul Winalski
2020-08-17 18:13 ` Jim Geist
2020-08-17 18:48 ` Paul Winalski
2020-08-17 19:08 ` Jim Geist
2020-08-17 19:28 ` Paul Winalski
2020-08-17 19:35 ` Jim Geist
2020-08-17 19:41 ` Richard Salz
2020-08-17 23:40 ` Steffen Nurpmeso
2020-08-17 19:27 Noel Chiappa
2020-08-17 19:30 ` Larry McVoy
2020-08-17 19:44 ` Dan Halbert
2020-08-17 19:50 ` Paul Winalski
2020-08-17 22:05 ` Arthur Krewat
2020-08-18 0:52 ` Rob Gingell
2020-08-17 19:51 Noel Chiappa
2020-08-17 22:32 Norman Wilson
2020-08-17 22:55 ` Bakul Shah
2020-08-17 23:12 ` Chet Ramey
2020-08-18 6:33 ` arnold
2020-08-25 9:36 Steve Simon
2020-08-26 13:24 Doug McIlroy
2020-08-26 15:41 ` John Cowan
2020-08-26 15:59 Noel Chiappa
2020-08-26 16:09 ` Warner Losh
2020-08-26 19:13 ` Clem Cole
2020-08-26 16:14 ` Jim Geist
2020-08-26 17:31 ` John Cowan
2020-08-27 8:37 Paul Ruizendaal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=107719ce-b631-c4c9-fedd-ac8845d01213@gmail.com \
--to=cym224@gmail.com \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).