Mark Geisert wrote:
[...]
Thanks for the report and investigations. I'll address this shortly.
A candidate patch for 3.4.7 is incoming. If it passes muster I'll fire off a
patch for 3.3.6. I don't know why I'm using military terminology. Independence
Day soon in the US, I guess.
Cheers,
Hi all,
Brian Inglis wrote:
On 2023-07-01 08:20, Jon Turney wrote:
On 14/03/2023 08:56, Mark Geisert wrote:
Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
Take the opportunity to follow FreeBSD's and Linux's lead in recasting
macro inline code as calls to static inline f
On 2023-07-01 08:20, Jon Turney wrote:
On 14/03/2023 08:56, Mark Geisert wrote:
Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
Take the opportunity to follow FreeBSD's and Linux's lead in recasting
macro inline code as calls to static inline functions. This allows the
mac
On 14/03/2023 08:56, Mark Geisert wrote:
Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
Take the opportunity to follow FreeBSD's and Linux's lead in recasting
macro inline code as calls to static inline functions. This allows the
macros to be type-safe. In addition, added
On Mar 14 01:56, Mark Geisert wrote:
> Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
>
> Take the opportunity to follow FreeBSD's and Linux's lead in recasting
> macro inline code as calls to static inline functions. This allows the
> macros to be type-safe. In addition, a
Addresses https://cygwin.com/pipermail/cygwin/2023-March/253220.html
Take the opportunity to follow FreeBSD's and Linux's lead in recasting
macro inline code as calls to static inline functions. This allows the
macros to be type-safe. In addition, added a lower bound check to the
functions that
