From: "J.A. Magallon" <jamagallon@able.es>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: x86 building altivec for raid ?
Date: Sun, 13 Nov 2005 22:02:13 +0100 [thread overview]
Message-ID: <20051113220213.55fc6fae@werewolf.auna.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
Hi all...
Long time ago noticed this, but did not remember to report till this night:
x86 seems to build altivec source files for md checksums:
CC drivers/md/raid6recov.o
CC fs/partitions/ldm.o
CC fs/proc/task_mmu.o
HOSTCC drivers/md/mktables
CC net/core/dev_mcast.o
UNROLL drivers/md/raid6int1.c
UNROLL drivers/md/raid6int2.c
UNROLL drivers/md/raid6int4.c
UNROLL drivers/md/raid6int8.c
UNROLL drivers/md/raid6int16.c
CC fs/proc/inode.o
UNROLL drivers/md/raid6int32.c
UNROLL drivers/md/raid6altivec1.c
UNROLL drivers/md/raid6altivec2.c
UNROLL drivers/md/raid6altivec4.c
UNROLL drivers/md/raid6altivec8.c
CC fs/partitions/msdos.o
CC drivers/md/raid6mmx.o
CC fs/proc/root.o
CC net/core/dst.o
LD fs/partitions/built-in.o
CC net/core/neighbour.o
CC drivers/md/raid6sse1.o
(buld lines are out of order due to a make -j4)
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.
Thanks.
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.1 (Cooker) for i586
Linux 2.6.14-jam2 (gcc 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-13 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 21:02 J.A. Magallon [this message]
2005-11-13 21:26 ` x86 building altivec for raid ? Neil Brown
2005-11-13 21:35 ` H. Peter Anvin
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=20051113220213.55fc6fae@werewolf.auna.net \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox