From: "H. Peter Anvin" <hpa@zytor.com>
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 ?
Date: Sun, 13 Nov 2005 13:35:42 -0800 [thread overview]
Message-ID: <4377B1AE.8070806@zytor.com> (raw)
In-Reply-To: <17271.44949.625740.612801@cse.unsw.edu.au>
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
next prev parent reply other threads:[~2005-11-13 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 21:02 x86 building altivec for raid ? J.A. Magallon
2005-11-13 21:26 ` Neil Brown
2005-11-13 21:35 ` H. Peter Anvin [this message]
2005-11-13 21:49 ` J.A. Magallon
2005-11-13 22:12 ` Sam Ravnborg
2005-11-13 22:33 ` J.A. Magallon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4377B1AE.8070806@zytor.com \
--to=hpa@zytor.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.