This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.2 altivec options and glibc
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 25 Aug 2002 12:19:49 -0400
- Subject: Re: gcc 3.2 altivec options and glibc
- References: <200208251616.MAA58758@bromo.msbb.uc.edu>
On Sun, Aug 25, 2002 at 12:16:34PM -0400, Jack Howarth wrote:
> Does anyone intimate with the gcc 3.2 altivec code
> generation options have a good feel for what would happen
> if glibc were recompiled with altivec code generation
> enabled in gcc 3.2? In particular, would the libm created
> by such a compile have its floating point operations
> redirected to the altivec? I am asking because we already have
> some code, hp-timing, that doesn't run on the 601, and it
> might be interesting at this point to explore an altivec
> saavy version of glibc. It seems to me that simply enabling
> its use through compiler flags would be a good starting
> point, no? Thanks in advance for any suggestions.
GCC does not automatically use Altivec instructions for anything. It
only enables the user to hand-code them without having to use assembly.
So far at least.
In addition, I believe support in 3.2 is a bit immature; the trunk is
MontaVista Software Debian GNU/Linux Developer