This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFAdvice - a couple of old lost Altivec patches
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Stan Shebs <shebs at apple dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>,Dale Johannesen <dalej at apple dot com>, <gcc at gcc dot gnu dot org>
- Date: Thu, 3 Oct 2002 00:33:06 -0400 (EDT)
- Subject: Re: RFAdvice - a couple of old lost Altivec patches
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.