DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 56T8dhtc615553
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 56T8dhtc615553
X-Recipient: archive-cygwin@delorie.com
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
Date: Tue, 29 Jul 2025 10:39:18 +0200
To: cygwin@cygwin.com
Subject: Re: new c++ new/delete overloads need wrapping?
Message-ID: <aIiItsyRODNPeqez@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <81535510-8360-1c72-442a-0b630a6d937f@jdrake.com>
 <aINAAW2oh-EfgP0V@calimero.vinschen.de>
 <d2b0c82b-7390-7efe-789f-8d11120ec12a@jdrake.com>
 <aIdBw5iSaIonAPbI@calimero.vinschen.de>
 <80497791-d323-4204-66ef-4b1a8ff45aa9@jdrake.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <80497791-d323-4204-66ef-4b1a8ff45aa9@jdrake.com>
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

On Jul 28 12:57, Jeremy Drake via Cygwin wrote:
> On Mon, 28 Jul 2025, Corinna Vinschen via Cygwin wrote:
> > Unless there's some automatism referencing the __wrap_X functions even
> > if the --wrap option isn't present, I don't see this incompatibility as
> > much of a problem.  We're trying to maintain backward compat, but that
> > doesn't mean an executable created under  and for a newer Cygwin DLL
> > has to run under an older DLL.
> 
> OK, then the patch adds support for wrapping these functions ends up in a
> stable Cygwin release, then GCC is updated to add additional --wrap
> parameters for them, and that GCC and binaries it produces will no longer
> be compatible with older Cygwin DLLs.

*iff* the --wrap option is used with functions not provided by older
DLLs, right?  Not for some reason generally incompatible, I hope...


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
