--Pd0ReVV5GZGQvF3a
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 24, 2005 at 12:00:37PM +0100, Martin Husemann wrote:
> That would be too weak - it's forbidden, unless you play special arch
> dependend tricks to allow it. Some archs do that for their memcpy/memset=
=20
> implementations. You will need to explicitly save and restore fpu state
> before and after your code and enable/disable the fpu.

Meaning it's completely disallowed?

> Let me ask the other obvious question: why do you implement the neural ne=
twork
> in the kernel?

Well, the network is used to calculate process priorities, so I think it
must be integrated in the scheduler.  Is there a better way to do this?

Regards,
Peter
--=20
http://www.student.kun.nl/peter.bex
--
"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
							-- Donald Knuth

--Pd0ReVV5GZGQvF3a
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCHbW9Lg33BXzVMqsRAoyjAJ0YYaAV2y65iZ0RV1nqvYCA3zxigwCgw3DO
TLv1kT8YHm8HrX61Djp4QKs=
=WsEY
-----END PGP SIGNATURE-----

--Pd0ReVV5GZGQvF3a--