From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12842 invoked by alias); 9 Jan 2013 05:25:08 -0000 Received: (qmail 12812 invoked by uid 22791); 9 Jan 2013 05:25:05 -0000 X-SWARE-Spam-Status: No, hits=-7.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 Jan 2013 05:24:57 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r095OuwA016509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Jan 2013 00:24:56 -0500 Received: from stumpy.slc.redhat.com (ovpn-113-50.phx2.redhat.com [10.3.113.50]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r095OtLa006599; Wed, 9 Jan 2013 00:24:55 -0500 Message-ID: <50ECFF27.5050305@redhat.com> Date: Wed, 09 Jan 2013 05:25:00 -0000 From: Jeff Law User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?UTF-8?B?SsO8cmdlbiBVcmJhbg==?= CC: Richard Sandiford , gcc-patches@gcc.gnu.org Subject: Re: Support for MIPS r5900 References: <20130106225645.190700@gmx.net> <87y5g43bkf.fsf@talisman.default> <50EB9EF4.9090804@redhat.com> <87mwwk2l6p.fsf@talisman.default> <20130108224924.27410@gmx.net> In-Reply-To: <20130108224924.27410@gmx.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg00465.txt.bz2 On 01/08/2013 03:49 PM, "Jürgen Urban" wrote: > > @Jeff: I think you know the stringent copyright rules for GCC. I want > to use the code from the original patch, but I don't know how many > people were involved. So I can't use it without copyright problems. > Can you please tell me which code can I use without encountering > copyright problems? I plan to submit the code for fixing the r5900 > short loop bug in GCC. If you're using something from the Cygnus port, then it would be covered by the blanket copyright assignment Cygnus had in place with the FSF. If there are any doubts about the origin of a hunk of GCC code I could probably pull out the old sources to determine if it came from Cygnus's code base or not. Jeff