From: adventures in9 <firstname.lastname@example.org>
Subject: Re: [9front] Port Status
Date: Tue, 5 Jul 2022 11:23:33 -0700 [thread overview]
Message-ID: <CAPfmpJD2ZhNv+fNJgAb4N4n3B1WGj4xXLfhORzyPFjW=3BKUSg@mail.gmail.com> (raw)
That's odd because my system has those spim files.
cpu% ls -l
--rw-rw-r-- M 683 theowner sys 1656 May 10 22:46 float.h
--rw-rw-r-- M 683 theowner sys 2249 May 10 22:46 math.h
--rw-rw-r-- M 683 theowner sys 366 May 10 22:47 stdarg.h
--rw-rw-r-- M 683 theowner sys 991 May 10 22:47 ureg.h
cpu% diff /spim/include/ape/stdarg.h /mips/include/ape/stdarg.h
For reference, my system was installed with Community vs
Infrastructure and then I used sysupdate for the latest release.
It might just be time to retire the 68k series. In my own recent
quest to find Raspberry Pi alternatives, the few 68k based chips still
produced seem to be stripped down models, often lacking MMU, used for
micro controller applications. Fujitsu still makes sparc based chips,
but says they will be ending production soon. And I wasn't able to
find anything in mass production based on open sparc.
Even though the Mips parent company has said they are switching to
risc-v, there are still several companies manufacturing mips cpus, and
a couple Chinese companies taking their license and expanding on them.
A new project I found interesting that used a Mips chips was this;
On Tue, Jul 5, 2022 at 7:57 AM <email@example.com> wrote:
> Quoth Frank D. Engel, Jr. <firstname.lastname@example.org>:
> > spim:
> > cpp: /sys/include/ape/fmt.h:26 ./libc.h:21 ctime.c:1 Could not find
> > include file <stdarg.h>
> Looks like spim is missing /spim/include/ape; I'm going to guess
> that it should be identical to /mips/include/ape.
next prev parent reply other threads:[~2022-07-05 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 1:25 Frank D. Engel, Jr.
2022-07-04 18:36 ` ori
2022-07-05 10:13 ` Frank D. Engel, Jr.
2022-07-05 14:53 ` ori
2022-07-05 18:23 ` adventures in9 [this message]
2022-07-07 3:16 ` Amavect
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).