/freebsd/lib/libstdthreads/ |
H A D | Symbol.map | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | call_once.c | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | cnd.c | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | tss.c | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | thrd_create.3 | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | threads.h | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | thrd.c | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | mtx.c | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
H A D | Makefile | fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|
/freebsd/lib/ |
H A D | Makefile | diff fc6f0665bae406f564e6eb6e1deea849d368a708 Mon Dec 26 22:51:53 CET 2011 Ed Schouten <ed@FreeBSD.org> Add libstdthreads.
This library implements the C11 threads interface on top of the pthreads library. As discussed on the lists, the preferred way to implement this, is as a separate library.
It is unlikely that these functions will be used a lot in the future. It would have been easier if the C11 working group standardized (a subset of) pthreads and clock_nanosleep(). Having it as a separate library allows the embedded people to omit it from their system.
Discussed on: arch@, threads@
|