[M3commit] CVS Update: cm3

Tony Hosking hosking at cs.purdue.edu
Fri Nov 5 16:10:27 CET 2010


It's an additional hurdle for installation.  There are some platforms where I don't have it already.
Once the gcc developers require C++ to install gcc's C compiler then I guess maybe this is moot.
We really should look at using LLVM!

On Nov 5, 2010, at 11:05 AM, Jay K wrote:

> 
> Do you really not have it already?
> The gcc developers are planning on using C++ in gcc, so the decision has been
> made, if we stick with gcc and upgrade to that. LLVM is also written in C++.
> (not that I plan on using it -- my real interest, again, is generating C, but then,
> rather C++, for exception handling)
> 
>  - Jay
> 
> ----------------------------------------
>> From: hosking at cs.purdue.edu
>> Date: Fri, 5 Nov 2010 09:52:25 -0400
>> To: jkrell at elego.de
>> CC: m3commit at elegosoft.com
>> Subject: Re: [M3commit] CVS Update: cm3
>> 
>> Umm, not a good plan. I don't want to install C++ just to build the backend!
>> 
>> On Nov 5, 2010, at 6:11 AM, Jay Krell wrote:
>> 
>>> CVSROOT: /usr/cvs
>>> Changes by: jkrell at birch. 10/11/05 06:11:12
>>> 
>>> Modified files:
>>> cm3/m3-sys/m3cc/src/: m3makefile
>>> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: Make-lang.in config-lang.in
>>> m3-def.h
>>> Added files:
>>> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.cpp
>>> Removed files:
>>> cm3/m3-sys/m3cc/gcc/gcc/m3cg/: parse.c
>>> 
>>> Log message:
>>> switch to C++, I want to use 'scope tricks' to avoid repeating the serialization macros in the handler functions -- the handlers will access member data instead
>> 
> 		 	   		  




More information about the M3commit mailing list