From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11710 invoked by alias); 3 Oct 2002 04:33:11 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11703 invoked from network); 3 Oct 2002 04:33:10 -0000 Received: from unknown (HELO mail.cdt.org) (206.112.85.61) by sources.redhat.com with SMTP; 3 Oct 2002 04:33:10 -0000 Received: from dberlin.org (pool-138-88-135-219.esr.east.verizon.net [138.88.135.219]) by mail.cdt.org (Postfix) with ESMTP id D5082490072; Thu, 3 Oct 2002 00:09:26 -0400 (EDT) Received: from [127.0.0.1] (HELO localhost) by dberlin.org (CommuniGate Pro SMTP 4.0b9a) with ESMTP-TLS id 460031; Thu, 03 Oct 2002 00:33:07 -0400 Date: Wed, 02 Oct 2002 21:48:00 -0000 From: Daniel Berlin To: Stan Shebs Cc: Zack Weinberg , Dale Johannesen , Subject: Re: RFAdvice - a couple of old lost Altivec patches In-Reply-To: <3D9B7E9B.7050405@apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-10/txt/msg00142.txt.bz2 On Wed, 2 Oct 2002, Stan Shebs wrote: > Zack Weinberg wrote: > > >On Wed, Oct 02, 2002 at 03:39:34PM -0700, Dale Johannesen wrote: > > > >>>This is a clearly desirable feature; the > >>>difficulty is, the routine is written to the old layout of > >>>CONST_VECTOR. I'm having trouble figuring out how to update it for > >>>the new one. Anyone have suggestions? > >>> > >>I can do better than that, we have it working. Unfortunately this patch > >>came originally from Motorola (according to my archive search here) and > >>is therefore off limits for FSF, last I heard. > >> > > > >I thought the copyright issues with the Motorola code had been > >resolved, but you may be more up on this than I am. Disappointing. > > > The last I remember, it was somewhat confused, but hopefully Kumar sees > this and clarifies for us. Of course, if you take old easy_vector_constant > bits of interest and simply rewrite them for the current code base, that > completely finesses the problem. (And if there is no other reasonable way > to express those old bits, then there is no creativity involved and thus > no copyright to worry about!) I actually have taken the program that generates the instruction sequences for all the 16 bit constants, and made it output what is necessary to use it in easy_vector_constant. Of course, it's *way* too big. If you like, however, I can just make it output a compact DFA we can walk to generate the vector constants.