From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17368 invoked by alias); 18 Apr 2011 12:20:46 -0000 Received: (qmail 17357 invoked by uid 22791); 18 Apr 2011 12:20:45 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_50,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Apr 2011 12:20:13 +0000 Received: from [213.157.30.140] (port=59751 helo=termi.gnu.org) by fencepost.gnu.org with esmtpa (Exim 4.71) (envelope-from ) id 1QBnR6-00007R-69 for gdb@sourceware.org; Mon, 18 Apr 2011 08:20:12 -0400 From: jemarch@gnu.org (Jose E. Marchesi) To: gdb@sourceware.org Subject: Work on the SIS ERC32 Emulator Date: Mon, 18 Apr 2011 12:20:00 -0000 Message-ID: <87k4erg3ip.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-04/txt/msg00090.txt.bz2 Hello. My employers decided to pay me to improve the 'sis' ERC32 emulator which is part of the gdb distribution (sim/erc32 in the redhat repo). In principle they will be paying 4 hours per week. The investment may be increased depending on the outcome of the activity. The main goals of the activity are: - To improve the performance of the emulator. We will start implementing the basic performance tricks: threaded code, caching of condition codes, etc. - To make the emulator flexible enough to simulate boards used in current spacecrafts. - Eventually, to advance 'sis' to emulate LEON2 and LEON3 as well as ERC32. Regarding licensing, - The copyright holder of the modified code would be my Employer. That seems reasonable given that SIS is copyrighted by ESA and/or Jiri Gaisler. - We would prefer to release the code under GPLv3+, but GPLv2+ would be fine as well. Are those goals and requirements compatible with your roadmap? We are or course willing to consider any technical suggestion you may have and to adapt to the development guidelines/policies of gdb. -- Jose E. Marchesi jemarch@gnu.org GNU Project http://www.gnu.org