This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Implicit altivec vs. linux kernel build
- From: Benjamin Herrenschmidt <benh at kernel dot crashing dot org>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: "'David Edelsohn'" <dje at watson dot ibm dot com>, "'Geoff Keating'" <geoffk at geoffk dot org>, gcc at gcc dot gnu dot org, "'Paul Mackerras'" <paulus at samba dot org>, "'Alan Modra'" <amodra at bigpond dot net dot au>
- Date: Tue, 01 Mar 2005 11:25:46 +1100
- Subject: RE: Implicit altivec vs. linux kernel build
- References: <SERRANOvMbRiFzDMOEp00000019@SERRANO.CAM.ARTIMI.COM>
> Surely it would be possible to use -ffixed-* options to reserve all the
> altivec registers and get precisely that effect?
Nah, I don't need to be that drastic. The RAID6 code is already in a
separate file that can have a specific additional set of compile flags,
so I can just enable altivec just for this file and make sure the
functions it provides are always called from the proper environment
(that is have the enable_kernel_altivec() call etc... be _outside_ of
that file).
Ben.