Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.modula2 > #137

Re: Lilith M2 compiler

Show all headers | View raw

On Oct 20, 2:31 pm, Rugxulo <rugx...@gmail.com> wrote:
> Hi,
>
> On Oct 20, 8:55 am, Michael McGaw <mikemt...@gmail.com> wrote:
>
>
>
> > I have been working on a port of the Lilith multipass M2 compiler,
>
> > what I am really interested in, is the so-called Single Pass
> > M2 compiler that generates M-Code.  This should make the problem of
> > moving the compiler much simpler, and improve the overall performance
> > of compilation as well.
>
> > I am wondering if there is anyone who reads this discussion group who
> > might either have the sources for this compiler and would be willing
> > to share them with me
>
> > I would greatly appreciate any feedback.
>
> I'm probably the wrong person to ask, but I think I remember reading
> on here that MacMETH derived from that compiler.
>
> http://www.sysecol.ethz.ch/RAMSES/MacMETH.html
>
> Possibly others too (M2Amiga), dunno. Chris Burrows is probably the
> guy who would know (at least more than I do).
>
> Sorry I can't help further. However, if all you want is faster speed,
> just put the compiler on a RAM disk. That's the only reason for extra
> speed anyways, right? It keeps it in RAM instead of constantly dumping
> back and forth between slow storage (HD).
>
> Just curious, what systems are you trying to get it working on?
>
>

Thanks- I have the MacMeth sources, and am somewhat familiar with the
overall project of Ramses.

Chris and I have been in conversation about this, also.  In fact, I
have been in conversation with a great many about this, and my post
here is sort of a 'last ditch, casting of a net' type of approach to
see if there's anyone who reads this list who might be able to point
me to where the single pass M-code generating version of this compiler
might be.

As for the systems on which I wish to use this: that's just it.  With
the port done reasonably well, it could be used just about anywhere.
Right now, I have an acceptable and working system, but, the porting
of the multipass compiler is not for the faint of heart, as pointers
and CARDINALs are presumed the same size and passed this way on the
interpass files.  There are many consequences of this meandering
through the compiler.  Takes a while to tease through all that.
Moreover, one needs to focus on hosting of the compiler on a specific
target, whereas the linker and interpreter are much easier to move
around.  The single pass compiler ought to make the portabilty problem
go away almost completely.

Lastly, again as to why do this: such a setup I think would be quite
useful for being able to continue to run M2 regardless what comes in
terms of computing targets.

-M

Back to comp.lang.modula2 | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Lilith M2 compiler Michael McGaw <mikemti99@gmail.com> - 2011-10-20 06:55 -0700
  Re: Lilith M2 compiler Rugxulo <rugxulo@gmail.com> - 2011-10-20 11:31 -0700
    Re: Lilith M2 compiler Michael McGaw <mikemti99@gmail.com> - 2011-10-21 05:49 -0700
      Re: Lilith M2 compiler George <george@invalid.invalid> - 2011-10-21 09:27 -0400
      Re: Lilith M2 compiler tbreeden <breedent@acm.org> - 2011-10-21 07:10 -0700
        Re: Lilith M2 compiler Michael McGaw <mikemti99@gmail.com> - 2011-10-21 10:00 -0700
  Re: Lilith M2 compiler jan272 <jan272@gmail.com> - 2011-10-22 02:23 -0700
    Re: Lilith M2 compiler "Chris Burrows" <cfbsoftware@hotmail.com> - 2011-10-22 23:16 +1030
      Re: Lilith M2 compiler jan272 <jan272@gmail.com> - 2011-10-22 10:49 -0700

csiph-web