Add a missing semicolon in src/io.c.

…tforms, like Android before API 28, that didn't have it

Keep posix_memalign() around for older Android APIs

Add an additional flag to indicate that `-lc` is sufficient for pthread
support and that `-lpthread` is not needed. This allows us to build with
newer NDKs.

build: android bundles pthread into libc

…ar places to use posix_memalign

from aligned_malloc. This was caught by thread sanitizer.

Switching back _dispatch_operation_perform to use posix_memalign from aligned_malloc

We should use build IDs on Linux so that we can identify the built
artefacts, and also so that we can match them up with debug
information should we choose to separate it.

rdar://130582819

Correct the comment for DISPATCH_MACH_MSG_DESTRUCTOR_VM_DEALLOCATE

…ate.h

Correct the comment DISPATCH_MACH_MSG_DESTRUCTOR_VM_DEALLOCATE at mach_private.h

Add more comments for #endif in .h file.

Should fix this properly, but for now just disable the warning itself.

Disable new `cast-function-type-mismatch`

[Linux] Enable build IDs.

`DispatchData.withUnsafeBytes` created a new `dispatch_data_t` by calling `dispatch_data_create_map`. I assume that the intention was that this memory was freed when `data` is destroyed, based on the presence of `_fixLifetime(data)` but `data` was just a plain `dispatch_data_t` C struct, that doesn’t have any cleanup operations associated with it when destroyed.

To fix the leak, wrap the `dispatch_data_t` in a `DispatchData`, which takes over the ownership of the `dispatch_data_t` and releases it when `data` gets destroyed.

Alternatively, `_fixLifetime` could have been replaced by `_swift_dispatch_release(unsafeBitCast(data, to: dispatch_object_t.self))` but I think using `DispatchData` is the cleaner solution.

Fix a memory leak in `DispatchData.withUnsafeBytes`

🍒[6.1] Handle multibyte path strings on Windows