X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B621D388A02B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1586221044;
	bh=HDRbwnbtGIehQMerEUFimMgg61huVIVXa3hG2TtFXWQ=;
	h=Subject:From:To:Date:In-Reply-To:References:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From;
	b=EP2psgO4Ha2IFahkLvhWUT2dNrb23VDaaDPxpUEIy/ANYtnkgPNOU5xaRfDqECSRq
	 JSepU+XK85iQUguO9HK2uwL6vFuR+TZYXVgG08BK0grXO/sor19qKnyNsC29YsHjUI
	 f3fxU5ecS05Eggmr05xHXnllk+vLGfLN5CMwZIjg=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org ABECE385BF83
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=cygwin.com
Authentication-Results: sourceware.org;
 spf=fail smtp.mailfrom=yselkowitz AT cygwin DOT com
X-MC-Unique: 8LUlzJ91MjKXLbYF6UYP7A-1
Message-ID: <1589e4d3f86e0fb8102ffa419af0d0ccf53d6cca.camel@cygwin.com>
Subject: Re: Problem in mingw64-i686-binutils [Was: Updated:
 binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)]
From: Yaakov Selkowitz <yselkowitz AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Date: Mon, 06 Apr 2020 20:57:07 -0400
In-Reply-To: <d77a6a7d-7ce1-1349-cc35-96f9f0213ef1@gmail.com>
References: <CAAXzdLWXD09FkgTmo2FY0kH4NmyYeAu9gnQaarkwYxKjYjOx3Q AT mail DOT gmail DOT com>
 <CAO1jNwvJsgL92nOdyTMfdL8_Rj211o=T3Aro=6PouDoM_T+X7g AT mail DOT gmail DOT com>
 <CAO1jNwtsZ_2JzydqvavfbNzn_xh-noU8EXSNG_xdrH_7fdt5=Q AT mail DOT gmail DOT com>
 <d77a6a7d-7ce1-1349-cc35-96f9f0213ef1 AT gmail DOT com>
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: cygwin.com
X-Spam-Status: No, score=-8.9 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NEUTRAL,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <http://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: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On Mon, 2020-04-06 at 23:55 +0000, JonY via Cygwin wrote:
> On 4/6/20 10:07 AM, Jan Nijtmans via Cygwin wrote:
> > Ping.
> > 
> > Would it be possible to release a version of mingw64-i686-binutils with the
> > same patch as done for binutils-2.34+1git.de9c1b7cfe-1? I suspect
> > this would resolve the problem described here.
> 
> Can you please report this issue to the binutils mailing list? I am
> unfamiliar with the binutils internals to know what exactly went wrong.

JonY,

I think the relevant differences after 2.34 were PR24511 and PR25447,
which are already fixed upstream:

https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=40bfb9762747f8336b17c70a0173d10200fa62eb
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=82f439d028c65663a0baf0a17ef5c4a2ea5c84a7

Adding those as patches to 2.34 should fix the issue without having to
resort to a git snapshot.

--
Yaakov


--
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