Re: Building latest Myrddin doesn't work

[Ryan Gonzalez <rymg19@xxxxxxxxx>]

Well...

I was looking at LLVM, but I'm not overly familiar with it. My main gripe
is that LLVM assembly isn't necessarily backwards-compatible; C, of course,
is.

Also, I figured a C backend would make Myrddin's future self-hosting
easier; you just distribute the compiled C sources, kind of like Nim does.
And C works on things such as Plan 9.

On the other hand, LLVM would *technically* be better. I've just seen too
many compilers (mostly Nim and RPython) try to use LLVM and end up
switching to C.

I'll start looking into it more now.

On Sun, Mar 8, 2015 at 11:43 PM, Ori Bernstein <ori@xxxxxxxxxxxxxx> wrote:

> On Sun, 8 Mar 2015 20:03:58 -0500
> Ryan Gonzalez <rymg19@xxxxxxxxx> wrote:
>
>
> > FYI, I recently wrote about the top 5 programming languages you've never
> > heard of
> > <
> http://kirbyfan64.github.io/posts/the-top-5-programming-languages-youve-never-heard-of-part-2.html
> >,
> > and I mentioned Myrddin as my favorite low-level language. :)
>
> Nice!
>
> I noticed you said that you were looking at writing a C backend. I'm
> wondering if you looked at doing LLVM instead? Writing LLVM assembly
> seems like it would be a better fit, thanks to a whole lot fewer
> instances of undefined behavior and similar.
>
> (Also, my plan is to write a self hosting compiler some time in the
> next year or so.)
>



-- 
Ryan
If I were in a 10-story building glass-sided building and forced to write
either Go or APL, I’d jump out a window.
http://kirbyfan64.github.io/