diff options
author | ed <ed@FreeBSD.org> | 2016-03-31 18:50:06 +0000 |
---|---|---|
committer | ed <ed@FreeBSD.org> | 2016-03-31 18:50:06 +0000 |
commit | 34d932442d51324e6fcc857f3b011ae003224974 (patch) | |
tree | 938629e0d00886bf52863a41daebabf369d9bb59 /secure | |
parent | 20ec114656780fa413a08040b90055b6d938ff32 (diff) | |
download | FreeBSD-src-34d932442d51324e6fcc857f3b011ae003224974.zip FreeBSD-src-34d932442d51324e6fcc857f3b011ae003224974.tar.gz |
Sync in the latest CloudABI system call definitions.
Some time ago I made a change to merge together the memory scope
definitions used by mmap (MAP_{PRIVATE,SHARED}) and lock objects
(PTHREAD_PROCESS_{PRIVATE,SHARED}). Though that sounded pretty smart
back then, it's backfiring. In the case of mmap it's used with other
flags in a bitmask, but for locking it's an enumeration. As our plan is
to automatically generate bindings for other languages, that looks a bit
sloppy.
Change all of the locking functions to use separate flags instead.
Obtained from: https://github.com/NuxiNL/cloudabi
Diffstat (limited to 'secure')
0 files changed, 0 insertions, 0 deletions