public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [HEADSUP] Phasing out old Windows versions and 32 bit support
Date: Wed, 27 Oct 2021 12:20:37 +0200	[thread overview]
Message-ID: <YXkn9bHOub6Pthy3@calimero.vinschen.de> (raw)
In-Reply-To: <5bd48f61-4ae5-22f1-7374-c374f5be689e@towo.net>

On Oct 27 11:37, Thomas Wolff wrote:
> Am 27.10.2021 um 10:49 schrieb Corinna Vinschen via Cygwin:
> > Less than 1% are real 32 bit systems.
> I think roughly 1% is still a community to consider. Working old machines
> shouldn't be trashed just because they are missing a few bits :)
> 
> > Dropping 32 bit support will reduce code complexity in Cygwin and it will
> > reduce the workload of the package maintainers.
> Code complexity was also an argument when dropping XP support, but there was
> quite some discussion at its time.

There's always discussion.  Supporting older systems gets unfeasible at
one point.  The hoops you have to jump through to get the same
functionality or just an adequate fake to replace stuff readily
available on later systems are in part considerable.  Just have a quick
look at clock.cc.  Practically all clock types need an OS check and a
workaround for older systems.

> For `egrep "# *if.*(32|64)"` I'm counting roughly 160 matches in winsup, but
> only in a few files. Is it really necessary?

Look again, just check for `# *if.*86' instead.  Ignoring the math
lib, 212 conditional compilations in 74 files, some of them really
tricky.  exceptions.cc is a nightmare in itself.  Plus the wrapper
functions still supporting Cygwin executables built under Cygwin 1.3,
which only affects 32 bit anyway.  If this can go away, the code base
will be *much* simpler and easier to understand and *maybe* it will help
to find somebody interested in sharing Cygwin maintainership.  We're all
not getting younger...

> > Those few still running
> > Cygwin on a real 32 bit system will still have a chance to run Cygwin
> > by utilizing Peter's time machine.
> 
> Peter's time machine is a very appreciable effort. It's a bit fiddly
> though to figure out how to use it, particularly to identify the
> "latest XP version". Maybe some explicit howto could be published on
> the cygwin pages?

Sure, if somebody wants to write up something, no problem to publish
it on the Cygwin website.


Corinna

  reply	other threads:[~2021-10-27 10:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 20:55 Corinna Vinschen
2021-10-26 22:01 ` [QUAR] " Eliot Moss
2021-10-26 22:52 ` Michel LaBarre
2021-10-27  4:29   ` Peter A. Castro
2021-10-27  8:53     ` Corinna Vinschen
2021-10-27 16:28       ` Peter A. Castro
2021-10-28  7:00         ` Corinna Vinschen
2021-10-27 14:57     ` Michel LaBarre
2021-10-27 16:38       ` Peter A. Castro
2021-10-27  8:33   ` Corinna Vinschen
2021-10-27  0:24 ` Takashi Yano
2021-10-27  8:49   ` Corinna Vinschen
2021-10-27  9:37     ` Thomas Wolff
2021-10-27 10:20       ` Corinna Vinschen [this message]
2021-10-27 16:46       ` Peter A. Castro
2021-10-27 21:04         ` Thomas Wolff
2021-10-27 23:35           ` Peter A. Castro
2021-10-27 13:07   ` Andrew Schulman
2021-10-27 11:03 ` L A Walsh
2021-10-27 11:10   ` Corinna Vinschen
2021-10-27 15:25 ` [HEADSUP] " Jim Reisert AD1C
2021-10-27 17:22   ` EXTERNAL: " Damon Register
2021-10-27 22:35 ` [HEADSUP] Phasing out old Windows versions and 32 bit support [XEmacs for 64-bit?] Dan Harkless
2021-10-27 22:37   ` Dan Harkless
2021-10-27 22:36 ` Dan Harkless
2021-10-28  8:47   ` Henry S. Thompson
2021-10-27 20:36 [HEADSUP] Phasing out old Windows versions and 32 bit support Jeremy Drake
2021-10-28  6:00 ` Brian Inglis
2021-10-28  7:11 ` Corinna Vinschen

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=YXkn9bHOub6Pthy3@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).