[M3devel] adding new target?

Fri Nov 4 19:08:29 CET 2011

Hi all:
well, but nonetheless, like first DEC pdp-10 didn't have those:
http://www.xkl.com/darkstar.html

Even today I doubt modern pdp-10 would have it or not, maybe I guess.
In retrospective you sort of fell like you could build your own OS for those big machines, even now, why wouldn't one think the same way. I think they even created paging hardware and basically the same sort of handling would depend on the OS itself as well to handle it (they had ported some Unix from AT&T and BSD of historic value but I don't know even a Linux distro that runs on it or something like that, well maybe some emulator).
http://en.wikipedia.org/wiki/SIMH#Digital_Equipment_Corporation

The interest on this stuff is the packet fields and BITS types of Modula-3, wouldn't be nice to have those on a recent hardware implementations? But then we would need to address the INTEGER issues, and etc (p.d they have ported gcc to there, so this is fact possible:
http://gcc.gnu.org/ml/gcc/2008-04/msg00516.html

)

Thanks in advance

--- El vie, 4/11/11, Jay K <jay.krell at cornell.edu> escribió:

De: Jay K <jay.krell at cornell.edu>
Asunto: RE: [M3devel] adding new target?
Para: dabenavidesd at yahoo.es, "m3devel" <m3devel at elegosoft.com>, "Mika Nystrom" <mika at async.caltech.edu>
Fecha: viernes, 4 de noviembre, 2011 12:39

 > does this MIPS have MMU-less chipI doubt it, but maybe.
I think even routers are "big" systems with MMUs.

 - Jay

> Date: Fri, 4 Nov 2011 16:28:29 +0000
> From: dabenavidesd at yahoo.es
> To: m3devel at elegosoft.com; mika at async.caltech.edu
> Subject: Re: [M3devel] adding new target?
> 
> Hi all:
> Does this MIPS have MMU-less chip, meaning, there are embedded linuses that run it:
> http://books.google.com/books?id=kk8G2gK4Tw8C&lpg=PA48&ots=c_1Nl4KtOw&dq=%22MMu-less%22%20mips&pg=PA49#v=onepage&q&f=false
> 
> This is a must in terms of addresanility, besides others like the endianess
> or sort for DS3100, etc re-configurable (weel not in hot but at driver level, like in SPARC:
> 
> http://www.fortunecity.com/skyscraper/motorola/22/resume.htm
> ).
> 
> At the bottom of this and newer SMp there are issues as in Intel, that might be need to be put in consideration for gcc or so:
> http://www.youtube.com/watch?v=WUfvvFD5tAA.
> 
> I don't know maybe that gcc for gnu/m3 was not a bad idea at all (fsf isn't helping that as well too much):
> http://users.crocker.com/~hudson/hudson.html
> 
> Thanks in advance
> 
> --- El vie, 4/11/11, Mika Nystrom <mika at async.caltech.edu> escribió:
> 
> > De: Mika Nystrom <mika at async.caltech.edu>
> > Asunto: [M3devel] adding new target?
> > Para: m3devel at elegosoft.com
> > Fecha: viernes, 4 de noviembre, 2011 02:30
> > Hi Jay,
> > 
> > I know you have mentioned before that it's now "easy" to
> > add a new target.
> > I would like to add a target that is already mostly there,
> > I think.
> > The one I want is mipsel-linux.  This is to run on an
> > Asus RT-N16 router
> > running OpenWRT or DD-WRT.  These devices have 500 MHz
> > MIPS processors
> > and 128 MB of DRAM.
> > 
> > First before you read this email, are there any
> > instructions for what
> > I'm trying to do anywhere, beyond your emails?  I am
> > using boot1.py
> > as you suggested.
> > 
> > What I did was the following (guesses all along):
> > 
> > made a cm3.cfg which I called MIPSEL_LINUX and put in 
> > m3-sys/cminstall/src/config-no-install:
> > 
> > ::::
> > readonly TARGET = "MIPSEL_LINUX" % code generation target
> > readonly GNU_PLATFORM = "mipsel-linux" % "cpu-os" string
> > for GNU
> > 
> > SYSTEM_CC = "gcc -gstabs+ -fPIC" % C compiler
> > SYSTEM_ASM = "as" % Assembler
> > 
> > m3back_m32 = "" % -m32 not allowed
> > 
> > include("MIPSEL.common")
> > include("Linux.common")
> > ::::
> > 
> > where MIPSEL.common contains:
> > 
> > ::::
> > 
> > readonly TARGET_ARCH = "MIPS"
> > readonly TARGET_ENDIAN = "LITTLE"   % {
> > "BIG" OR "LITTLE" }
> > readonly WORD_SIZE    = "32BITS"    % {
> > "32BITS" or "64BITS" }
> > 
> > ::::
> > 
> > Now I don't really know which of these strings are just
> > arbitrary
> > strings that I'm defining here and which of them have to
> > match
> > other things (and if so, what they have to match).
> > 
> > In any case I'm doing something wrong because I do (on a
> > FreeBSD4
> > machine)...
> > 
> > ./boot1.py MIPSEL_LINUX
> > 
> > which runs for a bit and eventually degenerates to
> > 
> > gmake[1]: Nothing to be done for `all'.
> > gmake[1]: Leaving directory
> > `/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3cc/FreeBSD4-I386_FREEBSD/libdecnumber'
> > cd ../FreeBSD4-I386_FREEBSD && cd libcpp &&
> > gmake  CFLAGS="-g
> > -O2"   MAKE=gmake  AUTOCONF=: AUTOMAKE=:
> > LEX='touch lex.yy.c' MAKEINFO=: libcpp.a |  tee -a
> > 
> > /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3cc/src/../FreeBSD4-I386_FREEBSD/_m3.log
> > cd ../FreeBSD4-I386_FREEBSD && cd libcpp &&
> > gmake  CFLAGS="-g
> > -O2"   MAKE=gmake  AUTOCONF=: AUTOMAKE=:
> > LEX='touch lex.yy.c' MAKEINFO=: libcpp.a |  tee -a
> > 
> > /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3cc/src/../FreeBSD4-I386_FREEBSD/_m3.log
> > gmake: `libcpp.a' is up to date.
> > cd ../FreeBSD4-I386_FREEBSD && cd gcc &&
> > gmake  CFLAGS="-g
> > -O2"   MAKE=gmake  AUTOCONF=: AUTOMAKE=:
> > LEX='touch lex.yy.c' MAKEINFO=: s-modes insn-config.h
> >  m3cg | tee -a
> > /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3cc/src/../FreeBSD4-I386_FREEBSD/_m3.log
> > cd ../FreeBSD4-I386_FREEBSD && cd gcc &&
> > gmake  CFLAGS="-g
> > -O2"   MAKE=gmake  AUTOCONF=: AUTOMAKE=:
> > LEX='touch lex.yy.c' MAKEINFO=: s-modes insn-config.h
> >  m3cg | tee -a
> > /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3cc/src/../FreeBSD4-I386_FREEBSD/_m3.log
> > gmake: `s-modes' is up to date.
> > gmake: `insn-config.h' is up to date.
> > gmake: Nothing to be done for `m3cg'.
> > --- building in FreeBSD4 ---
> > 
> > new source -> compiling RTHooks.i3
> > ../src/runtime/common/RTHooks.i3:15: fatal error:  ***
> > illegal type: 0x6f, at m3cg_lineno 5
> > compilation terminated.
> >   m3_backend => 1
> > m3cc (aka cm3cg) failed compiling: RTHooks.ic
> > new source -> compiling RT0.i3
> > ../src/runtime/common/RT0.i3:19: fatal error:  ***
> > illegal type: 0x6f, at m3cg_lineno 5
> > compilation terminated.
> >   m3_backend => 1
> > m3cc (aka cm3cg) failed compiling: RT0.ic
> > new source -> compiling RuntimeError.i3
> > ../src/runtime/common/RuntimeError.i3:10: fatal
> > error:  *** illegal type: 0x6f, at m3cg_lineno 5
> > compilation terminated.
> >   m3_backend => 1
> > ...
> > 
> >     Mika
> > 
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20111104/7587bd07/attachment-0002.html>