Message-ID: <4377B1AE.8070806@zytor.com>
Date: Sun, 13 Nov 2005 13:35:42 -0800
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
To: Neil Brown <neilb@suse.de>
CC: "J.A. Magallon" <jamagallon@able.es>,
       Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: x86 building altivec for raid ?
References: <20051113220213.55fc6fae@werewolf.auna.net> <17271.44949.625740.612801@cse.unsw.edu.au>
In-Reply-To: <17271.44949.625740.612801@cse.unsw.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 837
Lines: 24

Neil Brown wrote:
> On Sunday November 13, jamagallon@able.es wrote:
> 
>>Kernel is 2.6.14-mm2.
>>This is an x86 box, why does it compile raid6altivec*.c ? I suppose it
>>does not generate any code, because of some #ifdef magic, but why does
>>it build them anyways ? Looks a bit strange.
> 
> It's probably just easier that way.
> I guess you could do the following, but I'm not sure that it is really
> worth it.
> 

Yes, it's really just simpler.  It ends up being an empty .o file on 
non-altivec machines.

I don't object to changing it, but it doesn't seem worth it to change it.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/