public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chris Roehrig <croehrig@house.org>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.1.9814cfd8f693 (TEST)
Date: Sat, 18 Sep 2021 12:03:15 -0700	[thread overview]
Message-ID: <FB2D2A59-62F8-4CFA-B9B5-A5496ABFF518@house.org> (raw)
In-Reply-To: <announce.387113a9-3652-5dac-17be-70ce1f4f68b8@cornell.edu>


I'm not sure how to try out a test release without risking destabilizing my system, but I re-cloned and rebuilt the master branch and installed just the cygwin1.dll and all looks good to me so far.   No issues with any of my script pipes or fifos and I am getting full gigabit speeds with rsync.  

I too have been following all the pipe rework on Cygwin-developers and want to express my appreciation for Takashi, Ken and Corinna for tackling this.    You folks have made Cygwin so much more usable for a lot of applications!

-- Chris


On Fri Sep 17 2021, at 1:33 PM, Ken Brown via Cygwin-announce via Cygwin <cygwin@cygwin.com> wrote:

> The following packages have been uploaded to the Cygwin distribution as test releases:
> 
> * cygwin-3.3.0-0.1.9814cfd8f693
> * cygwin-devel-3.3.0-0.1.9814cfd8f693
> * cygwin-doc-3.3.0-0.1.9814cfd8f693
> 
> This release comes with an overhaul of the internal pipe code.  In theory, there should be no user-visible changes except for bug fixes and performance improvements.  But of course there will be new bugs.  Please test!
> 
> =======================================================================
> 
> What's new:
> -----------
> 
> - An IP-sampling profiler named 'profiler' has been added.  It can be
>  used to profile any Cygwin program along with any DLLs loaded.
> 
> - A new tool 'gmondump' has been added.  It can dump the raw
>  information of any "gmon.out" file created by profiler, ssp, or use
>  of the gcc/g++ option '-pg'.  (Continue using gprof to get symbolic
>  profile displays.)
> 
> - New GNU-specific APIs, slated to become part of the next POSIX
>  standard:  pthread_cond_clockwait, pthread_mutex_clocklock,
>  pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock,
>  sem_clockwait.
> 
> - New Solaris-specific APIs, slated to become part of the next POSIX
>  standard:  sig2str, str2sig.
> 
> 
> What changed:
> -------------
> 
> - The speed argument to cfsetspeed(3) can now be a numerical baud rate
>  rather than a Bnnn constant, as on Linux.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-July/248887.html
> 
> - The internal implementation of pipes has been overhauled; this
>  should result in improved performance.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-August/249238.html
> 
> 
> Bug Fixes
> ---------
> 
> - Fix values returned by select(2) for shutdown sockets.
>  Addresses: https://cygwin.com/pipermail/cygwin-developers/2021-April/012092.html
> 
> - Introduce a new hypotl(3) function not suffering unnecessary
>  overflows.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-April/248302.html
> 
> - Fix path handling for paths spanning native symlinks.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-April/248307.html
> 
> - Fix tab position evaluation after console window resize.
> 
> - Fix a regression in pseudo console handling, resulting in rlwrap not
>  being able to start a new pseudo console.
> 
> - Handle two race conditions in pseudo console usage.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-April/248292.html
> 
> - Fix a bug in recognizing a successful completion of connect(2) on a
>  datagram socket.
> 
> - Fix connect(2) when called with an address structure whose family is
>  AF_UNSPEC.  As specified by POSIX and Linux, this is allowed on
>  datagram sockets, and its effect is to reset the socket's peer
>  address.
> 
> - Fix nanosleep(2) returning negative rem. NtQueryTimer appears to be
>  able to return a negative remaining time (less than the timer
>  resolution) for unsignalled timers.
> 
> - Fix getifaddrs(3) returning address family 0 or IPv4 address 0.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-July/248970.html
> 
> - Fix getaddrinfo(3) to return valid ai_socktype and ai_protocol
>  values if the underlying GetAddrInfoW screws up.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-July/248985.html
> 
> - Fix duplicate /proc/partitions entries and (presumably) duplicate
>  PIDs in ps(1) output.
>  Addresses: https://cygwin.com/pipermail/cygwin/2021-July/248998.html
>             https://cygwin.com/pipermail/cygwin/2021-August/249124.html
> 
> =======================================================================
> 
> 
> Have fun,
> 
> Ken Brown, on behalf of Corinna
> 
> -- 
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple


  parent reply	other threads:[~2021-09-18 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 20:33 Ken Brown via Cygwin-announce
2021-09-18 15:33 ` Achim Gratz
2021-09-18 19:03 ` Chris Roehrig [this message]
2021-09-18 20:17   ` Ken Brown
2021-09-18 20:01 ` Denis Excoffier
2021-09-18 20:20   ` Ken Brown
2021-09-18 21:30     ` Thomas Wolff
2021-09-18 22:32       ` Ken Brown
2021-09-19  0:49         ` Hans-Bernhard Bröker
2021-09-19  6:42           ` ASSI
2021-09-19 12:27             ` Ken Brown
2021-09-19 13:32               ` Thomas Wolff
2021-09-19 14:42                 ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FB2D2A59-62F8-4CFA-B9B5-A5496ABFF518@house.org \
    --to=croehrig@house.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).