[M3commit] CVS Update: cm3

[Jay Krell]

CVSROOT:	/usr/cvs
Changes by:	jkrell at birch.	09/01/28 18:44:42

Modified files:
	cm3/m3-libs/m3core/src/runtime/ALPHA_OSF/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/AMD64_DARWIN/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/FreeBSD4/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/I386_DARWIN/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/LINUXLIBC6/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/NetBSD2_i386/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/PPC_DARWIN/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/SOLgnu/: RTThread.m3 
	cm3/m3-libs/m3core/src/runtime/SOLsun/: RTThread.m3 

Log message:
	eliminate more gratuitous platform differences
	
	Some platforms uses + to combine mprotect protections, some used Word.Or.
	Use + because it is terser, assuming these are all independent flags.
	
	Some platforms used WITH i = foo; ASSERT(i = 0);
	Some used VAR i := foo; ASSERT(i = 0);
	Use VAR, in order to elminate indentation.
	
	some platforms said IF (page_size = 0) and some said IF page_size = 0.
	Use the second shorter form. This code kinda looks like it has a race condition,
	but probably not, since it is the code that is involved in creating threads,
	there cannot be multiple threads until after it runs.
	
	Platforms still vary as to what protections they use on the last stack page.