On Mon, Dec 15, 2014 at 4:53 AM, Maciej Fijalkowski <fij...@gmail.com> wrote: > > On Mon, Dec 15, 2014 at 9:22 AM, Maciej Fijalkowski <fij...@gmail.com> > wrote: > > On Mon, Dec 15, 2014 at 6:35 AM, Ryan <rym...@gmail.com> wrote: > >> I don't know; it just seems weird, since LLVM and libgccjit seem to hold > >> similar concepts (though there's a 99% chance I'm wrong; I just glanced > over > >> the libgccjit description). > >> > >> What I *really* wish PyPy could have would be a C-- backend. *That* > would be > >> insanely awesome and would probably blow the C backend out of the water. > > > > You seem to have a lot of opinions. Can you back this one up with > something? >
I like to experiment with stuff that probably won't work. Can't help it. > > To clarify my question: > > C-- looks like a cool idea, but not very actively developed. I would > expect to run into bugs or just missing features. Some parts are > obviously more suited for compilers than say C, but I would expect GCC > (and to some extent LLVM) to be more mature and have better > optimizations. I would need to see some evidence of C-- being used by > someone else than original author before trying to evaluate it. > > Which is why I said *I wish*. It probably won't happen because Quick C-- (the only C-- compiler) has been abandoned. I think C-- would be great because it has an awesome runtime interface. You can traverse the stack, gather roots, mark specific variables as roots and others as non-roots...all built-in. > Cheers, > fijal > -- Ryan If anybody ever asks me why I prefer C++ to C, my answer will be simple: "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was nul-terminated." Personal reality distortion fields are immune to contradictory evidence. - srean Check out my website: http://kirbyfan64.github.io/
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
