Earlier quoted context omitted.
There are perfectly legitimate reasons to put a network interface controller into promiscuous mode [1], and it's nothing to be ashamed of, and perfectly acceptable to discuss at conferences. Back in the "bad old days" of the simplex NCP protocol [2], before the duplex TCP/IP protocol legalized same-sex network connections, connect and listen sockets had gender defined by their parity, and all connections were require…
I don't see where the socket numbers are added. You test ac3 which is loaded from consck, but where does that come from? Or did you mean the code you linked to with "The PDP-10 code above"?
That's weird that it does several different types of moves in a row into the same register -- there must be some kind of implicit calculation going on, or maybe it's just a bug.
I'd use "git blame" to bug-shame whoever wrote that heterosexist code, but I don't think they were using safe source code control practices back then.