DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 524A9piA3347913
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 524A9piA3347913
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=V2/pmSKz
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org A42753858D28
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1741082988;
	bh=EZRVDp1+0YzeNEknJbVXspm9ce1ChBw5FCCyNLvxMx0=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=V2/pmSKzevtvkbmPIs7SWcBkJhXfcq8xmSHmaFtGPJ8n6wuQ6s8ViiEqSHX0vywqs
	GhcWPekJWDicu9V9z6ahCfjJzj/xv6fwKIcIwGdMXNV1LjOatYECgAaAioFiu+gmfx
	lqaXwXXVRos28SddzLogxkbEKpWVH2OeSSsnO9hU=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 810F63858D21
Date:	Tue, 4 Mar 2025 11:08:49 +0100
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin 3.6: Supporting 128 POSIX realtime (SIGRTMAX-SIGRTMIN >=
	128) signals?
Message-ID:	<Z8bRMfg87ZSWfscd@calimero.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAPJSo4V-o3uXn7kFo1T93keo1w_SVTsGVEdycOfQDQC-L4KZCA AT mail DOT gmail DOT com>
	<Z8WVxlEujfFlRrVn AT calimero DOT vinschen DOT de>
	<CAPJSo4X0Vt3SafShOiQFNnR3oFCi2ZjRiutEMpeeyESp2XbtkA AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAPJSo4X0Vt3SafShOiQFNnR3oFCi2ZjRiutEMpeeyESp2XbtkA@mail.gmail.com>
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Mar  3 23:07, Lionel Cons via Cygwin wrote:
> On Mon, 3 Mar 2025 at 12:43, Corinna Vinschen via Cygwin
> <cygwin AT cygwin DOT com> wrote:
> >
> > On Feb 28 15:36, Lionel Cons via Cygwin wrote:
> > > We've hit a scalability issue in Cygwin today, the application in
> > > question ran out of POSIX realtime signals (i.e. SIGRTMIN-SIGRTMAX).
> > >
> > > Could Cygwin support 128 POSIX realtime signals?
> >
> > Not possible.  sigset_t is an unsigned long, thus we can only support
> > up to 64 signals.
> >
> > A change to a bigger sigset_t is an ABI breakage and requires two
> > different entry points for all functions touching the sigset_t type, one
> > for the new definition of sigset_t, one for backward compatibility with
> > existing applications.  This *could* be part of 3.7, but I don't make
> > any promises.
> 
> gcc has int128_t - would that help you?

Not at all.  It doesn't change the underlying problem of the ABI breakage.


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

- Raw text -