From: random832@fastmail.us (random832@fastmail.us)
Subject: [TUHS] speaking of early C compilers
Date: Mon, 27 Oct 2014 09:40:36 -0400 [thread overview]
Message-ID: <1414417236.2834739.183752501.006CD61F@webmail.messagingengine.com> (raw)
In-Reply-To: <5BDD9EB6-4F00-4C28-BC7F-4A264996A625@ronnatalie.com>
On Mon, Oct 27, 2014, at 09:34, Ronald Natalie wrote:
> Yep, the kernel was littered with funky memory constants using -> to
> point at various registers. Probably the most ubuiqtous was
> #define PS 0177776
> struct {
> int integ;
> };
>
> yielding the PS->integ access to the Processor Status Register.
Is there any reason this is superior to *(int *)0177776 [and e.g.
#define integ(x) (*(int *)(x))]? Did casting not exist back then?
next prev parent reply other threads:[~2014-10-27 13:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:32 Jason Stevens
2014-10-27 13:03 ` Brantley Coile
2014-10-27 13:34 ` Ronald Natalie
2014-10-27 13:40 ` random832 [this message]
2014-10-27 14:04 ` Clem Cole
2014-10-27 15:04 ` Dave Horsfall
2014-10-27 17:09 ` scj
2014-10-27 20:35 ` Ronald Natalie
2014-10-27 21:34 ` Clem Cole
2014-10-28 1:09 ` Dave Horsfall
2014-10-28 2:06 ` Clem Cole
2014-10-28 12:22 ` Ronald Natalie
2014-10-28 12:42 ` Clem Cole
2014-10-28 13:03 ` Ronald Natalie
2014-10-28 22:02 ` John Cowan
2014-10-27 13:46 Noel Chiappa
2014-10-27 13:54 Jason Stevens
2014-10-27 14:48 Noel Chiappa
2014-10-27 15:09 ` Ronald Natalie
2014-10-27 15:13 ` Dave Horsfall
2014-10-27 16:52 ` Dan Cross
2014-10-27 15:48 Noel Chiappa
2014-10-27 16:25 ` Dave Horsfall
2014-10-28 0:16 ` John Cowan
2014-10-27 16:50 Norman Wilson
2014-10-27 18:16 Nelson H. F. Beebe
2014-10-28 1:55 Jason Stevens
2014-10-28 12:52 ` Ronald Natalie
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=1414417236.2834739.183752501.006CD61F@webmail.messagingengine.com \
--to=random832@fastmail.us \
/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).