From: macbiesz@optonline.net (macbiesz@optonline.net)
Subject: [TUHS] 32I status as of 17 Nov 2003
Date: Mon, 17 Nov 2003 19:13:47 -0500 [thread overview]
Message-ID: <185bd17fae.17fae185bd@optonline.net> (raw)
Perhaps v7upgrade would make a nice combination with the 32I kernel.
http://www.southern-storm.com.au/v7upgrade.html
Maciek
> >
> > 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.
>
> There are a couple of options here. One is to use one of the
> compilersfrom MIT that will match the code in 32V very closely.
> You can google for
> these if they aren't already on Warren's site. The other option
> is to use LCC. I wouldn't use GCC if I were doing it. (Of course
> I'm not
> so these are just suggestions.)>
next reply other threads:[~2003-11-18 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 0:13 macbiesz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 16:40 patv
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
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=185bd17fae.17fae185bd@optonline.net \
--to=macbiesz@optonline.net \
/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).