[M3devel] cm3, NOPTHREAD

[Jay K]

 > no, since we've lost self-hosted compiler (because PTHREADS is C code)  
 > when compiling using PTHREADS capabilities. 
 

 Again Daniel, this make no sense to me. 


> You need a new compiler image 


 
 Again Daniel, this is wrong.   


 
  >  and a new RT image 




  Again Daniel, this doesn't make complete sense to me.   
  What do you mean "new RT image"? 


 You need m3core, and then because its interface essentially changes (different type ids for thread and/or lock), you have to recompile everything else that you are going to use, with this new m3core -- i.e.  the entire dependency graph up to and including the executable.


You do NOT need a new compiler.
If it works, great. But you don't need it.


If we hide the types behind object or such, then only m3core will need to be rebuild. That is the plan. And more so -- a command line to change between them.
For now, the type ids vary.


-DNOPTHREAD only directly changes m3core.
The rest of the system can be compiled w/ or w/o it. But the new m3core causes a need for some rebuild.


 - Jay


________________________________
> Date: Fri, 25 May 2012 21:57:56 +0100 
> From: dabenavidesd at yahoo.es 
> Subject: Re: [M3devel] cm3, NOPTHREAD 
> To: dragisha at m3w.org 
> CC: jay.krell at cornell.edu; m3devel at elegosoft.com 
>  
> Hi all: 
> no, since we've lost self-hosted compiler (because PTHREADS is C code)  
> when compiling using PTHREADS capabilities. 
> You need a new compiler image and a new RT image, if you want to do  
> that; what you say, sounds like you can change that at build time, this  
> is not the case. 
> Thanks in advance 
>  
>  
> --- El vie, 25/5/12, Dragiša Durić <dragisha at m3w.org> escribió: 
>  
> De: Dragiša Durić <dragisha at m3w.org> 
> Asunto: Re: [M3devel] cm3, NOPTHREAD 
> Para: "Daniel Alejandro Benavides D." <dabenavidesd at yahoo.es> 
> CC: "Jay K" <jay.krell at cornell.edu>, "m3devel" <m3devel at elegosoft.com> 
> Fecha: viernes, 25 de mayo, 2012 15:51 
>  
> Daniel, 
>  
> BUILDARGS is applied to all builds occuring while it's set. 
>  
> Have a nice day. 
>  
> dd 
>  
> On May 25, 2012, at 10:46 PM, Daniel Alejandro Benavides D. wrote: 
>  
> Hi all: 
> such system will not compile everything using NOPTHREAD thing, but  
> merely the compiler, so this doesn't help anything else than the  
> compiler, if you want to build with your compiler that then you need a  
> correct boot image. 
> Thanks in advance 
>  
>  
> --- El jue, 24/5/12, Dragiša Durić  
> <dragisha at m3w.org<http:///mc/compose?to=dragisha%40m3w.org>> escribió: 
>  
> De: Dragiša Durić  
> <dragisha at m3w.org<http:///mc/compose?to=dragisha%40m3w.org>> 
> Asunto: Re: [M3devel] cm3, NOPTHREAD 
> Para: "Jay K"  
> <jay.krell at cornell.edu<http:///mc/compose?to=jay.krell%40cornell.edu>> 
> CC: "m3devel"  
> <m3devel at elegosoft.com<http:///mc/compose?to=m3devel%40elegosoft.com>> 
> Fecha: jueves, 24 de mayo, 2012 03:43 
>  
> I did 
>  
> export BUILDARGS="-DNOPTHREAD" 
>  
> before building packages/compiler. 
>  
> Didn't work. Built cm3 failed on first invocation with stack of three  
> elements, topmost being NoteStackLocations. No other data. 
>  
> On May 24, 2012, at 1:07 AM, Jay K wrote: 
>  
> Do you mean did we make something "official" and put it somewhere to be  
> tested and downloaded by the masses of Modula-3 programmers who want to  
> use both Modula-3 and user threads? I don't think so. 
>  
>  
> Do it yourself? 
>    (Try out scripts/python/make-dist.py?) 
>  
>  
> It has always been easy from a m3makefile point of view to do it. 
> You either use -DNOPTHREAD or such, or edit m3core/src/thread/m3makefile. 
>  
>  
>  
>