Unix, C, int-32-bits and... hardware architecture assumptions
sur-behoffski <[email protected]> Fri, 31 Jul 2026 14:45:40 +0930
| Newsgroups | gmane.comp.lang.lua.general |
|---|---|
| Message-ID | <[email protected]> |
G'day,
UNIX and C grew up together, on a PDP-11 system. In particular,
types became especially important when a floating-point processor
became available.
In the modern world, with "GNU/Linux" becoming more prominent
than "UNIX" (with POSIX in there as well), the compiler and OS
libraries have become more carefully defined.
The real world has moved away, quite considerably, from the naive
model of the PDP-11 hardware.
There's a keynote address from USENIX ATC '21, that shows how
e.g. "QualPwn" can exploit this: A malicious wi-fi packet can
potentially gain access to all of system memory via the SMMU
of the wi-fi connection, bypassing any other MMU infrastructure:
"USENIX ATC '21/OSDI '21 Joint Keynote Address-It's Time
for Operating Systems to Rediscover Hardware
[36myc8wQhLo].webm"
(Presenter: Prof.(CS) Timothy Roscoe, ETH Zurich.)
The address gives a number of other examples where the naive view
does not match real-world reality... and ways in which they're
building hardware to address issues (e.g. a server-like board that
runs several hundreds-of-thousands of lines of code, before the
CPU comes out of reset).
The video is quite comprehensive, at about an hour long.
----
In some ways, this reference is tangential to the very recent
discussion about 32-bit int shifts, C89, POSIX and C99.
However, I believe that Lua, especially because of its small
footprint and being attractive to embedded-systems applications,
is slowly growing into more such situations. (Adoption of
64-bit integers is one "recent" example of this.)
I believe that the "semi-static" MCU MRAM discussion is another
example of where the OS/Kernel and Lua are gradually
overlapping.
Hope this helps, s-b etc.
--
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/6cc3a27e-f178-426a-afff-3a03b9f63b5a%40grouse.com.au.