From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53091) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QywtB-0007Vs-9E for qemu-devel@nongnu.org; Wed, 31 Aug 2011 22:20:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QywtA-0003PW-Ee for qemu-devel@nongnu.org; Wed, 31 Aug 2011 22:20:21 -0400 Received: from dns1.mips.com ([12.201.5.69]:33586) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QywtA-0003PL-6a for qemu-devel@nongnu.org; Wed, 31 Aug 2011 22:20:20 -0400 Received: from exchdb01.mips.com (exchhub01.mips.com [192.168.36.84]) by dns1.mips.com (8.13.8/8.13.8) with ESMTP id p812KHlJ000319 for ; Wed, 31 Aug 2011 19:20:18 -0700 Message-ID: <4E5EEBDE.2020806@mips.com> Date: Wed, 31 Aug 2011 19:20:14 -0700 From: reed kotler MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] python scripts List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: "r >> \"Fuhler, Rich\"" , "Johnson, Eric" I recently made a major addition (about 150 new instructions) to MIPS QEMU to add the DSP instructions for Mips and Micro MIPS processors. To make this process simpler and less error prone, I generated a large amount of the code and framework from python scripts. This code is much easier to produce and maintain. I.e. python scripts producing C code and header files. I would like to check the python scripts along with the changes to autoconf into QEMU and have the build process produce the C code. We have another large project where we want to use this same technique again. Is there any big objection to this? The python is very simple and would probably work with python version 0.1. Of course the configure script can test for a proper python being present.