acadia-newlib/winsup/cygwin/release/3.1.7

Bug Fixes:
----------

- Fix acl_get_* functions in 32-bit Cygwin (pointer sign extension)

- Fix select/poll issue in case a socket connect call fails.
  Addresses: https://cygwin.com/pipermail/cygwin/2020-July/245528.html

- Fix multiple reader support for FIFOs
  Addresses: https://sourceware.org/pipermail/cygwin/2020-July/245456.html

- Fix an mmap issue that could cause failure with errno EFBIG
  Partially addresses: https://sourceware.org/pipermail/cygwin/2020-July/245557.html

- Fix the behavior of C++ apps after an unhandled exception (64-bit only)
  Addresses: https://cygwin.com/pipermail/cygwin/2019-October/242795.html
             https://cygwin.com/pipermail/cygwin/2020-August/245897.html
Fix invalid acl_entry_t on 32-bit Cygwin If the acl_t struct was at or above 0x80000000 then the pointer was sign-extended to 0xffff_ffff_8000_0000 and so the index was lost. Signed-off-by: David Allsopp <david.allsopp@metastack.com> 2020-07-09 12:17:03 -07:00			`Bug Fixes:`
			`----------`

			`- Fix acl_get_* functions in 32-bit Cygwin (pointer sign extension)`
Cygwin: document previous poll/select patch Signed-off-by: Corinna Vinschen <corinna@vinschen.de> 2020-07-16 01:58:40 -07:00
			`- Fix select/poll issue in case a socket connect call fails.`
			`Addresses: https://cygwin.com/pipermail/cygwin/2020-July/245528.html`
Cygwin: FIFO: document recent fixes 2020-07-16 13:21:03 -07:00
			`- Fix multiple reader support for FIFOs`
			`Addresses: https://sourceware.org/pipermail/cygwin/2020-July/245456.html`
Cygwin: mmap: document recent bugfix 2020-07-21 14:57:37 -07:00
			`- Fix an mmap issue that could cause failure with errno EFBIG`
			`Partially addresses: https://sourceware.org/pipermail/cygwin/2020-July/245557.html`
Cygwin: main exception handler (64-bit): continue GCC exceptions This is necessary in order to be consistent with the following comment in the definition of _Unwind_RaiseException() in the GCC source file libgcc/unwind-seh.c: The exception handler installed in crt0 will continue any GCC exception that reaches there (and isn't marked non-continuable). Previously we failed to do this and, as a consequence, the C++ runtime didn't call std::terminate after an unhandled exception. This fixes the problem reported here: https://cygwin.com/pipermail/cygwin/2019-October/242795.html https://sourceware.org/pipermail/cygwin/2020-August/245897.html 2020-08-17 13:24:59 -07:00
			`- Fix the behavior of C++ apps after an unhandled exception (64-bit only)`
			`Addresses: https://cygwin.com/pipermail/cygwin/2019-October/242795.html`
			`https://cygwin.com/pipermail/cygwin/2020-August/245897.html`