[qcc] TODO?

[Sean Lynch]

Hi, everyone. I thought I'd unsubscribed from this list since there are no
messages since May, but when I tried to resubscribe it told me I was
already subscribed, and sure enough the archives show no messages since May.

I started trying to use the "mob" branch of tinycc in a project, but so far
I am not having very good success. In particular, it looks like there is
not a way to use shared objects with TCC_OUTPUT_MEMORY without manually
adding the symbols, which defeats a large part of my purpose, which was to
have a runtime-compiled language that can directly use shared libraries by
embedding C.

In general, the lack of ownership of tinycc makes me nervous about hitching
my wagon to it. But a fast, in-memory C compiler definitely seems ideal for
my purposes. One of the many half-finished, abandoned code generation
backends out there would potentially get me a JIT but without easy access
to C shared objects. In that case, I might as well write my language using
RPython and resign myself to manually writing wrappers or at best
autogenerating them with a bunch of manual tweaking.

QCC seems like exactly what I'm looking for. I'd like to contribute, though
I will need to go through a process to get my employer (Google) to disclaim
copyright to any of my contributions that relate to their business (just
once for the whole project, hopefully). I could also contribute financially
through Bountysource or something if someone wants to set it up and that
would give people extra time/incentive to work on QCC.

It would be helpful if someone (I assume that would be Bruce since Rob
isn't listed as a contributor) could write a TODO file that's a little more
amenable to consumption by someone who's not yet familiar with the codebase
than the XXX and HIHI(?) comments and TODO section in qcc.c. Such a file
would double as a status report for anyone (like me) following development.

Thanks for working on this! This is a very underserved space since gcc or
LLVM work "well enough" for most people. Actually they work fantastically
as long as it's not runtime code generation you're interested in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.landley.net/pipermail/qcc-landley.net/attachments/20151006/0b32455e/attachment.htm>