public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Dropping 32 bit Cygwin? (was Re: segfault on 32bit)
Date: Wed, 8 Apr 2020 10:45:18 +0200	[thread overview]
Message-ID: <20200408084518.GP3261@calimero.vinschen.de> (raw)
In-Reply-To: <20200408083443.GN3261@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

On Apr  8 10:34, Corinna Vinschen wrote:
> Right.  This looks like a fork problem.  It's 32 bit, so we have to
> expect fork errors more often.
> 
> Given how much the distro has grown, and given that the number of 32 bit
> systems is constantly shrinking, we should really start to think about
> dropping 32 bit support.
> 
> Most users these days use 64 bit systems.  Some use 32 bit Cygwin on 64
> bit systems, which doesn't really make sense, except, maybe, to build 32
> bit packages.  These users can easily switch to 64 bit Cygwin.
> 
> The access statistics indicate that real 32 bit systems only make less
> than 2% of installed systems.  It's a lot of hassle to keep 32 bit
> Cygwin running for only a minor installation base.
> 
> I'm not saying that we switch off 32 bit support right now, but maybe
> 2020 should be the last year of 32 bit support.

Oh, btw., time_t on 32 bit Cygwin is only 32 bit wide, so the end is
near: 2038-01-19 03:14:07 UTC.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-04-08  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 17:33 segfault on 32bit Marco Atzeri
2020-04-07 20:27 ` Csaba Ráduly
2020-04-08  8:34   ` Dropping 32 bit Cygwin? (was Re: segfault on 32bit) Corinna Vinschen
2020-04-08  8:45     ` Corinna Vinschen [this message]
2020-04-08  8:53       ` Sharuzzaman Ahmat Raslan

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=20200408084518.GP3261@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).