[M3commit] CVS Update: cm3

[Jay K]

attached

----------------------------------------
> Date: Mon, 26 Jul 2010 15:44:59 +0000
> To: m3commit at elegosoft.com
> From: jkrell at elego.de
> Subject: [M3commit] CVS Update: cm3
>
> CVSROOT: /usr/cvs
> Changes by: jkrell at birch. 10/07/26 15:44:59
>
> Modified files:
> cm3/m3-libs/m3core/src/atomic/: m3makefile
> cm3/m3-libs/m3core/src/runtime/common/: Compiler.tmpl
> cm3/m3-libs/m3core/src/unix/Common/context/setjmp/: m3makefile
> cm3/m3-sys/m3cc/src/: platforms.quake
> cm3/m3-sys/m3middle/src/: Target.i3 Target.m3
> cm3/scripts/: sysinfo.sh
> cm3/scripts/python/: pylib.py
> Added files:
> cm3/m3-libs/m3core/src/C/MIPS64EL_OPENBSD/: Csetjmp.i3
> m3makefile
> cm3/m3-sys/cminstall/src/config-no-install/: MIPS64EL_OPENBSD
>
> Log message:
> add MIPS64EL_OPENBSD (e.g. Loongon/Gdium/Lemote)
> complete with:
> no atomics for 1 byte or 2 bytes
> no unwind tables (internal compiler error)
> These are for hypothetical future better exception handling, so ok.
> no debug symbols (there was a problem?)
> Should try again.
> user mode threads
> and worse, jmpbuf hacking
> need to try again the sigaltstack approach
> no Java => no Hudson
>
> Enough to build a cm3 that reports the expected "unable to find cm3.cfg".
>
> see:
> http://www.openbsd.org/loongson.html
> search web for: "Amazon gdium"
> etc.
>
> Presumably MIPS64EL_LINUX will fair a bit better.
>
 		 	   		  
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mips64el_openbsd.txt
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20100726/95ae4d9b/attachment-0002.txt>