From: patv@monmouth.com (patv@monmouth.com)
Subject: [TUHS] 32I status as of 17 Nov 2003
Date: Mon, 17 Nov 2003 11:40:24 EST [thread overview]
Message-ID: <200311171640.hAHGeOwB024089@wwws.monmouth.com> (raw)
1. Converted unpublished locore to AT&T syntax. Work still underway on
new locore.S file.
2. Will use coff executable format. May comply with Sys V ABI. The
latter is TBD.
3. Gcc is tool chain unless someone wants to take on 32V compiler. May
take advantage of inline and asm in machine dependent files.
I wouldn't recommend using the 32V compiler, mainly because there
are so many syntax changes, as well as newer compiler technology,
missing from it as to make it a very challenging project.
4. Gcc cross compile to be used for building. I'll make this available
later next month, after I shake out the bugs.
5. May go to Bitkeeper for source control. More to follow.
6. License for all new files to be the "revised BSD license." This is
compatible with the Caldera license, an "original BSD license" with
the advertising clause specific to Caldera. I want to keep it open
source, and this is the best compromise I see for project license.
7. May change spln() to more understandable nomenclature, e.g., spl4()
becomes spltty(), similar to BSD practice.
8. 32I is the interim name. I would have preferred Unix version 7, but
can't for obvious trademark reasons.
Project name still up for grabs. I was thinking of UNX, named after
the old DEC name for the facility I work in. Sort of a tribute to
days gone by, as is porting 32V. Probably get into trouble for that
one as well.
---------------------------------------------
This message was sent using Monmouth Internet MI-Webmail.
http://www.monmouth.com/
next reply other threads:[~2003-11-17 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 16:40 patv [this message]
2003-11-17 21:41 ` Brantley Coile
2003-11-17 22:17 ` M. Warner Losh
2003-11-17 22:48 ` Brantley Coile
2003-11-17 23:20 ` M. Warner Losh
2003-11-18 3:40 ` Pat Villani
2003-11-18 3:19 ` Pat Villani
2003-11-18 0:13 macbiesz
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=200311171640.hAHGeOwB024089@wwws.monmouth.com \
--to=patv@monmouth.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).