Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This isn't present at all on (older?) literal Darwin, and additionally fsync()
there doesn't actually flush writes to storage like it does on Linux. So, use
F_FULLFSYNC which was invented as an alternative API to do this.
|
|
According to include-what-you-use 0.20 (7301b1f) based on clang 16.0.6.
|
|
|
|
If some error happened here, there's nothing we can do but proceed and try to
copy anyway.
|
|
These are usually quite large, over 128 bytes.
|
|
|
|
|
|
|
|
It seems that certain versions and/or configurations of gcc warn about these
for static functions, which is annoying, but whatever.
|
|
|
|
This puts more onus on the build system to do things properly, but it's still
easy enough to build, even manually: all the files in the appropriate system
subdirectory just need to be included in the build.
Otherwise, the several nested levels of preprocessor conditionals get
confusing, and clang-format doesn't format code properly.
|