From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Seth McDonald <sethmcmail@pm.me>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: origin of alloca(3) (was: Undocumented systems/standards PWB and 32V)
Date: Fri, 2 Jan 2026 01:27:03 +0100 [thread overview]
Message-ID: <aVcQo73f4mT4NT_-@devuan> (raw)
In-Reply-To: <20260101235310.fejv4d7uvft7unzt@illithid>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi Branden,
On Thu, Jan 01, 2026 at 05:53:10PM -0600, G. Branden Robinson wrote:
> > 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? :)
Yup; I guess we could change PWB to PWB1 in the HISTORY of alloca(3).
Thanks!
Cheers,
Alex
>
> Regards,
> Branden
>
> [1] I see some other familiar stuff here...
>
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/sys/source/s4/stdio
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-02 0:27 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 ` origin of alloca(3) (was: Undocumented systems/standards PWB and 32V) G. Branden Robinson
2026-01-02 0:27 ` Alejandro Colomar [this message]
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=aVcQo73f4mT4NT_-@devuan \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--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