From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] Line Terminators in Text Files [
Date: Mon, 04 Sep 2017 20:28:27 +0000 [thread overview]
Message-ID: <CAP6exYL9WuknUFSuc0eVyQ7HXEuzTkqt9NcfRB+n05jSLaF-RA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NEc+V9mb2HJwtC_dmNJY61=0mgDdrnk=O=DOANMBJrGw@mail.gmail.com>
with one exception, Clem. Forsyth's port of Ken's C compiler let you
allocate r14 and r15 for your own purposes. Hence in Plan 9 they were used
for 'current process' and 'current core'. As I understand it gcc allows
this too.
Every once in a while it's nice to have that level of control. We gave it
up when we got plan 9 running with gcc and clang and it was painful ...
ron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170904/2bce00b7/attachment-0001.html>
next prev parent reply other threads:[~2017-09-04 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 20:06 Clem Cole
2017-09-03 21:42 ` Warner Losh
2017-09-04 17:29 ` Paul Winalski
2017-09-04 18:34 ` Clem Cole
2017-09-04 20:28 ` ron minnich [this message]
2017-10-01 17:24 ` Tom Ivar Helbekkmo
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=CAP6exYL9WuknUFSuc0eVyQ7HXEuzTkqt9NcfRB+n05jSLaF-RA@mail.gmail.com \
--to=rminnich@gmail.com \
/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).