| /freebsd/sys/arm/include/ |
| H A D | ieeefp.h | diff a50079b7ff232bbc45443ec0f1763fd449cea9a8 Fri Oct 21 08:41:46 CEST 2011 David Schultz <das@FreeBSD.org> People porting FreeBSD to new architectures ought not have to
implement a deprecated FPU control interface in addition to the
standard one. To make this clearer, further deprecate ieeefp.h
by not declaring the function prototypes except on architectures
that implement them already.
Currently i386 and amd64 implement the ieeefp.h interface for
compatibility, and for fp[gs]etprec(), which doesn't exist on
most other hardware. Powerpc, sparc64, and ia64 partially implement
it and probably shouldn't, and other architectures don't implement it
at all.
|
| /freebsd/sys/powerpc/include/ |
| H A D | ieeefp.h | diff a50079b7ff232bbc45443ec0f1763fd449cea9a8 Fri Oct 21 08:41:46 CEST 2011 David Schultz <das@FreeBSD.org> People porting FreeBSD to new architectures ought not have to
implement a deprecated FPU control interface in addition to the
standard one. To make this clearer, further deprecate ieeefp.h
by not declaring the function prototypes except on architectures
that implement them already.
Currently i386 and amd64 implement the ieeefp.h interface for
compatibility, and for fp[gs]etprec(), which doesn't exist on
most other hardware. Powerpc, sparc64, and ia64 partially implement
it and probably shouldn't, and other architectures don't implement it
at all.
|
| /freebsd/include/ |
| H A D | ieeefp.h | diff a50079b7ff232bbc45443ec0f1763fd449cea9a8 Fri Oct 21 08:41:46 CEST 2011 David Schultz <das@FreeBSD.org> People porting FreeBSD to new architectures ought not have to
implement a deprecated FPU control interface in addition to the
standard one. To make this clearer, further deprecate ieeefp.h
by not declaring the function prototypes except on architectures
that implement them already.
Currently i386 and amd64 implement the ieeefp.h interface for
compatibility, and for fp[gs]etprec(), which doesn't exist on
most other hardware. Powerpc, sparc64, and ia64 partially implement
it and probably shouldn't, and other architectures don't implement it
at all.
|
| /freebsd/sys/amd64/include/ |
| H A D | ieeefp.h | diff a50079b7ff232bbc45443ec0f1763fd449cea9a8 Fri Oct 21 08:41:46 CEST 2011 David Schultz <das@FreeBSD.org> People porting FreeBSD to new architectures ought not have to
implement a deprecated FPU control interface in addition to the
standard one. To make this clearer, further deprecate ieeefp.h
by not declaring the function prototypes except on architectures
that implement them already.
Currently i386 and amd64 implement the ieeefp.h interface for
compatibility, and for fp[gs]etprec(), which doesn't exist on
most other hardware. Powerpc, sparc64, and ia64 partially implement
it and probably shouldn't, and other architectures don't implement it
at all.
|
| /freebsd/sys/i386/include/ |
| H A D | ieeefp.h | diff a50079b7ff232bbc45443ec0f1763fd449cea9a8 Fri Oct 21 08:41:46 CEST 2011 David Schultz <das@FreeBSD.org> People porting FreeBSD to new architectures ought not have to
implement a deprecated FPU control interface in addition to the
standard one. To make this clearer, further deprecate ieeefp.h
by not declaring the function prototypes except on architectures
that implement them already.
Currently i386 and amd64 implement the ieeefp.h interface for
compatibility, and for fp[gs]etprec(), which doesn't exist on
most other hardware. Powerpc, sparc64, and ia64 partially implement
it and probably shouldn't, and other architectures don't implement it
at all.
|