Home
last modified time | relevance | path

Searched hist:a18c313e (Results 1 – 7 of 7) sorted by relevance

/freebsd/sys/powerpc/include/
H A Dsetjmp.ha18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
H A Dpcb.ha18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
/freebsd/sys/powerpc/ofw/
H A Drtas.ca18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
/freebsd/sys/powerpc/powerpc/
H A Dcopyinout.ca18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
H A Dmp_machdep.ca18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
H A Dtrap.ca18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
/freebsd/sys/powerpc/powermac/
H A Dgrackle.ca18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.
a18c313e Sun Jan 10 16:42:14 GMT 2016 Nathan Whitehorn <nwhitehorn@FreeBSD.org> Use setjmp() instead of the identical-except-for-having-a-wrong-prototype
setfault() when testing for faults. This should also help the compiler
do the right thing with this complicated-to-optimize function.