[M3devel] m3 backends and builtin types?

[Tony Hosking]

There is a bootstrap issue here isn’t there?  You need the compiler to inform the runtime of information that the compiler needs...

On Aug 15, 2012, at 6:11 PM, Jay K <jay.krell at cornell.edu> wrote:

> Something seems off to me in the current implementation.
> Like, I don't think the backends are ever informed of various "builtin" types, such as integer, word, char, widechar, boolean, mutex.
> I hardcoded knowledge of them in parse.c and M3C.m3.
> That seems wrong.
> 
> 
> Either that, or they are used before they are defined -- which might not be avoidable in general, but could easily be avoided for most types.
> 
> 
> Shouldn't m3front inform the backend via m3cg of these types?
> It is doable using the existing interfaces? 
> 
> 
> More so, RTBuiltin.mx ought not exist, right?
> Whatever data it contains should be built up like any other type data?
> Part of the same problem?
> 
> 
>  - Jay



Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Mobile +1 765 427 5484





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120815/cbba2af1/attachment-0002.html>