… | |
… | |
4757 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
4757 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
4758 | assumes that the same (machine) code can be used to call any watcher |
4758 | assumes that the same (machine) code can be used to call any watcher |
4759 | callback: The watcher callbacks have different type signatures, but libev |
4759 | callback: The watcher callbacks have different type signatures, but libev |
4760 | calls them using an C<ev_watcher *> internally. |
4760 | calls them using an C<ev_watcher *> internally. |
4761 | |
4761 | |
|
|
4762 | =item pointer accesses must be thread-atomic |
|
|
4763 | |
|
|
4764 | Accessing a pointer value must be atomic, it must both be readable and |
|
|
4765 | writable in one piece - this is the case on all current architectures. |
|
|
4766 | |
4762 | =item C<sig_atomic_t volatile> must be thread-atomic as well |
4767 | =item C<sig_atomic_t volatile> must be thread-atomic as well |
4763 | |
4768 | |
4764 | The type C<sig_atomic_t volatile> (or whatever is defined as |
4769 | The type C<sig_atomic_t volatile> (or whatever is defined as |
4765 | C<EV_ATOMIC_T>) must be atomic with respect to accesses from different |
4770 | C<EV_ATOMIC_T>) must be atomic with respect to accesses from different |
4766 | threads. This is not part of the specification for C<sig_atomic_t>, but is |
4771 | threads. This is not part of the specification for C<sig_atomic_t>, but is |
… | |
… | |
5004 | |
5009 | |
5005 | =back |
5010 | =back |
5006 | |
5011 | |
5007 | =head1 AUTHOR |
5012 | =head1 AUTHOR |
5008 | |
5013 | |
5009 | Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson. |
5014 | Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael |
|
|
5015 | Magnusson and Emanuele Giaquinta. |
5010 | |
5016 | |