On 7/20/2010 6:14 PM, Blue Swirl wrote:
If you keep the development process open, with patches, RFCs and other
proposals flowing regularly to upstream QEMU, I'd suppose the
developer community would welcome this. But there have been several
forks of QEMU and merging those looks hard. The problem
gt;
> Original Message ----
> Subject: [Qemu-devel] Automatic generation of code-generator components
> Date: Tue, 13 Jul 2010 14:09:56 -0400
> From: Eliot Moss
> Reply-To: m...@cs.umass.edu
> To: qemu-devel@nongnu.org
>
> Dear QEMU developers --
>
> I have had
Dear developers -- I've seen no responses yet. My proposal
is due in early August, so if anyone has feelings on this or
comments about it, please respond soon :-) ...
Thank you for your patience -- Eliot moss
Original Message
Subject: [Qemu-devel] Automatic generation of
Dear QEMU developers --
I have had some email conversation with a few active developers,
and with their encouragement, want to open it up for the whole list
to comment.
For several years my research group at UMass has been developing
generic code-generator generator (CGG) technology. Historic CG
