From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seth McDonald <sethmcmail@pm.me>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: origin of alloca(3) (was: Undocumented systems/standards PWB and 32V)
Date: Thu, 1 Jan 2026 17:53:10 -0600 [thread overview]
Message-ID: <20260101235310.fejv4d7uvft7unzt@illithid> (raw)
In-Reply-To: <aVZwLk0RWoyRjL8N@devuan>
[-- Attachment #1: Type: text/plain, Size: 2356 bytes --]
Hi Alex,
At 2026-01-01T14:17:35+0100, Alejandro Colomar wrote:
> Hi Branden, Seth,
>
> On Wed, Dec 31, 2025 at 11:46:32PM -0600, G. Branden Robinson wrote:
> > Hi Seth,
> >
> > At 2026-01-01T04:45:28+0000, Seth McDonald wrote:
> > > Starting the year off strong, here's a classic bug report. The man
> > > page for alloca(3) lists two systems/standards in its HISTORY: PWB and
> > > 32V.
> > >
> > > $ man ./man3/alloca.3 | sed -n '/HISTORY/,/^$/p'
> > > HISTORY
> > > PWB, 32V.
> > >
> > > After some Googling, I assume these are referring to the PWB/UNIX and
> > > UNIX/32V operating systems, respectively.
> >
> > Yes. Most likely. I have some remarks on nomenclature, orthography,
> > and history.
> >
> > PWB stands for "Programmer's Workbench". It was a flavor of Unix
> > maintained and sustained outside of the Bell Labs Computing Science
> > Research Center (CSRC) in Murray Hill, New Jersey. The CSRC is where
> > Unix was born and where famous names like Ken Thompson, Dennis Ritchie,
> > and Brian Kernighan worked. Eventually, the flavor of Unix produced by
> > the CSRC came to be known as "Research Unix". In the late 1980s the
> > CSRC decided that the Unix system was an unrewarding vehicle for further
> > _research_, and shifted its emphasis to Plan 9. Over time, the Jack
> > Welch-ification of AT&T[1] meant that research at Bell Labs became less
> > ambitious and eventually halted.
> >
> > PWB came in at least two revisions--the original, retro-branded PWB1,
> > and a second, sometimes called "PWB/UNIX 2.0".
>
> It would be good to check in which one alloca(3) was present.
There's _an_ `alloca()` in PWB/Unix 1.0.
https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/util/alloca.s
It's not declared in any header file I can find, and as you can see it's
written in PDP-11 assembly, but it's there, and appears to do what a
modern C programmer would expect of it.[1]
It appeared to get stuck into a library called "libpw.a".
Static, of course, because there were no shared libraries back then.
https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/util/makefile
Close enough? :)
Regards,
Branden
[1] I see some other familiar stuff here...
https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/stdio
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-01 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 4:45 Undocumented systems/standards PWB and 32V Seth McDonald
2026-01-01 5:46 ` G. Branden Robinson
2026-01-01 13:17 ` Alejandro Colomar
2026-01-01 23:53 ` G. Branden Robinson [this message]
2026-01-02 0:27 ` origin of alloca(3) (was: Undocumented systems/standards PWB and 32V) Alejandro Colomar
2026-01-02 0:24 ` Undocumented systems/standards PWB and 32V Alejandro Colomar
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=20260101235310.fejv4d7uvft7unzt@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=sethmcmail@pm.me \
/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