From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30014 invoked by alias); 15 Jan 2007 19:39:05 -0000 Received: (qmail 30001 invoked by uid 22791); 15 Jan 2007 19:39:04 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 15 Jan 2007 19:38:53 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l0FJcpig031304; Mon, 15 Jan 2007 14:38:51 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l0FJcjrH030502; Mon, 15 Jan 2007 14:38:45 -0500 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l0FJcjGr016349; Mon, 15 Jan 2007 14:38:45 -0500 Received: from ton.toronto.redhat.com (ton.toronto.redhat.com [172.16.14.15]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 6AA0D8001CA; Mon, 15 Jan 2007 14:38:45 -0500 (EST) Received: from ton.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by ton.toronto.redhat.com (8.13.1/8.13.1) with ESMTP id l0FJcj6t024724; Mon, 15 Jan 2007 14:38:45 -0500 Received: (from fche@localhost) by ton.toronto.redhat.com (8.13.1/8.13.1/Submit) id l0FJciKF024723; Mon, 15 Jan 2007 14:38:44 -0500 Date: Mon, 15 Jan 2007 19:39:00 -0000 From: "Frank Ch. Eigler" To: Joern Rennecke Cc: cgen@sources.redhat.com Subject: Re: copyright issues for cgen-generated tools Message-ID: <20070115193844.GA22188@redhat.com> References: <20070115113749.GA27642@elsdt-razorfish.arc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070115113749.GA27642@elsdt-razorfish.arc.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Mailing-List: contact cgen-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00005.txt.bz2 Hi, Joern - Long time no see. On Mon, Jan 15, 2007 at 11:37:49AM +0000, Joern Rennecke wrote: > We (ARC International) are currently evaluating the feasibility of using > cgen to generate simulators and binutils for the ARCompact family of cores. > The desired outcome is that the gdb sim simulator and binutils will be > integrated into the FSF mainline tree. OK. > [...] However, the cgen framework and cpu files that are recommended > as templates to writing your own cpu file (m32r is directly > recommended, and I've also found relevant bits for features not > covered in m32r.cpu in arc*.cpu, sh*.cpu sparc*.cpu and xstormy.cpu) > are copyright Red Hat. Of course you're not obligated to use these templates. Plus a bunch of these cpu/opc files have been donated to the FSF copyright pile; see the src/cpu directory for those. > I'm not sure to what extend the generated files are then copyright > Red Hat. [...] They aren't really; cgen is just too naive to properly mark up its generated code. IMO, if it can't propagate a copyright-holder tag from the input files into the outputs, it should not emit copyright notices at all. > Also, I'm not sure if the FSF requires the cgen source code to be > assigned to them. [...] Apparently not, but I wasn't privy to those early discussions when the first cgen-based binutils/gdb ports appeared. > There are copies of some old cgen cpu files in the sourceware.org > main tree which purport to be copyright FSF, but at the same time > the master copies in the cgen repository don't carry any FSF > copyright notices [...] That does not pose a problem. The copyright holder for the old .cpu files (Red Hat) has signed over many of those files, and happened to keep around some of the older versions. There is too little development going on to be too worried about master copy-ness or whatnot. I believe the gist of the situation is this. Write your model within the cpu/ directory. Use cgen to generate your binutils/simulator/whatnot into opcodes/ etc. If the copyright messages cgen emits are not correct ((C) FSF presumably), then edit them before submitting the inputs and outputs. Don't worry about the cgen program proper. Or something like that. - FChE