[M3devel] multi-threaded m3front?

[Jay K]

There are clearly three speeds to the compiler in my informal observation.
 The NT386 backend is fastest.  The m3cg backend is medium.  The C backed is a little slower.

But if this can all be divided by number of cores, and the I/O overlapped,they might all be fast. :)

I would like to write more integrated backends, but the C backend needs a bit more work,and we want to remove setjmp/longjmp for most targets still,and the existing M3x86.m3 has a terrible debugging story -- only line numbers.

 - Jay



> Date: Tue, 11 Aug 2015 14:46:35 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] multi-threaded m3front?
> 
> On Tue, Aug 11, 2015 at 10:20:26AM -0700, Darko Volaric wrote:
> > I couldn't agree with you more. I think being able to compile or cross
> > compile the system without spending hours (or days) hacking
> > scripts/environments would be a huge step forward for the project. Or
> > having compiler binaries for more than two platforms (four if you count
> > different word sizes). Meanwhile I've never heard anyone complain that the
> > compiler is too slow.
> 
> I'm even pleased how *fast* the compiler is.
> 
> If I could make it generate portable C, it would satisy most of the 
> uses I can imagine for it, not just the uses I actually have.
> 
> -- hendrik
> _______________________________________________
> M3devel mailing list
> M3devel at elegosoft.com
> https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150811/5357abf3/attachment-0002.html>