--Signature_Mon__2_Jan_2006_17_27_03_-0500_ugzZAxyC.wtoPBJ2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> Okay.  I guess my real question then is should this be being passed
> when I have commented out Altivec support in the kernel =20
> configuration?  I thought it might be a bug in the makefile or =20
> something.

Depends, -Wa,-maltivec only enables AltiVec mnemonics for the assembler
- it shouldn't actually produce AltiVec code on its own ( in fact gcc3
can't use AltiVec without help, passing -maltivec to the compiler
enables a few datatypes and C-mappings for AltiVec instructions but it
won't generate AltiVec instructions from regular C code ). But there's
definitely something fishy with 3.99.15 - all newer kernels cr*p out
right after startup on my G3, some kernel option must trigger it since
GENERIC works.=20

options ALTIVEC just makes sure the kernel knows and cares about AltiVec
registers on context switches so they can be safely used in userland
code if I remember correctly. Not sure if it does anything else.

have fun
Michael

--Signature_Mon__2_Jan_2006_17_27_03_-0500_ugzZAxyC.wtoPBJ2
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQ7mot8pnzkX8Yg2nAQJAoQf/VH0V5cXBtQ9kbeJosUCdXFYn4lbxf+MN
ZZYNWySlblgixgULzNYK8tszsbi0g9KUnX7+6R33wgd7JFdEJYMVq3PEtcjjCLn6
jqVlR1xoz8CBRExQGINJ+Vh70oP5FOYHkGDFKc4P8udco/E2EHJUxB+zcE/yY5je
uH45+trTTsI2qVmaAXrm1B/rXaVp87czlEJPQUUOJB4ZkrZGXVfMEzJ6xRKfehUg
YE2sF5NWPWaoDHu5MwulhjffNyRJIn9EuEA7w2VxwRXavHjxlkdizWp9e8Auwvay
gamUCHc5ZZU744h1hNWwrjQdtdpr+k6y9Qd8QYrFWDOETSrYh+U/Ew==
=j8gg
-----END PGP SIGNATURE-----

--Signature_Mon__2_Jan_2006_17_27_03_-0500_ugzZAxyC.wtoPBJ2--