X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 3CEFB3860C37
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=nexgo.de
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=Stromeko AT nexgo DOT de
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=nexgo.de;
	s=vfde-smtpout-mb-15sep; t=1612207438;
	bh=AkKg9wESLS7mal6FgIfL3Lz21pcTVG+EVTqvsFYW8kw=;
	h=From:To:Subject:References:Date:In-Reply-To;
	b=puwZ3J8JOhwsae2prUDRfPwBm/hRks01c3pQR5Akeactlwl3MBRpLy6h8BOW2TvMh
	UVUN/gN4bf/zMM5QB+YqhsZdDuf8YtZeO952XiKqOEiIWvNModEda7t6n9CcqYKQhb
	EFYNtG8Dad5BdN/xKLpyO1vyIf1te+fOFa6t9IpE=
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Random assembler errors after update
	mingw64-x86_64-binutils-2.35.2-1
References:	<announce DOT 87o8h52pnz DOT fsf AT Rainer DOT invalid>
	<f4d1da5f-897f-0b81-f474-65725c8bf1df AT yahoo DOT de>
Date:	Mon, 01 Feb 2021 20:23:49 +0100
In-Reply-To:	<f4d1da5f-897f-0b81-f474-65725c8bf1df@yahoo.de> (Michael Soegtrop
	via Cygwin's message of "Mon, 1 Feb 2021 10:25:57 +0100")
Message-ID:	<875z3bpp6i.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
MIME-Version:	1.0
X-purgate-type:	clean
X-purgate-Ad:	Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate:	This mail is considered clean (visit http://www.eleven.de for
	further information)
X-purgate:	clean
X-purgate-size:	1026
X-purgate-ID:	155817::1612207438-0000768F-EA1DEB19/0/0
X-Spam-Status:	No, score=-2.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham 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
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>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

Michael Soegtrop via Cygwin writes:
> I have some evidence that this update leads to random assembler
> errors. I have 3 CI failures (out of 5 runs) since the update in an
> open source project I maintain. The failure is always an error from
> the MinGW 64 assembler and the errors are random - that is if I rerun
> the same CI test the error went away in one of one tested case and in
> the failing cases the error happened compiling different files.

Unless you have something I can reproduce I'm afraid there's nothing I
can do.  You can try reporting upstream to see if somebody else has seen
someting like that before or try bisecting.

> I haven't seen anything like this before the update.
>
> Here are links to one failing and one good case:

None of them work for anybody who is not logged in to GitHub.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
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 -