From: Michael Soegtrop <MSoegtrop@yahoo.de>
To: cygwin@cygwin.com
Subject: Random assembler errors after update mingw64-x86_64-binutils-2.35.2-1
Date: Mon, 1 Feb 2021 10:25:57 +0100 [thread overview]
Message-ID: <f4d1da5f-897f-0b81-f474-65725c8bf1df@yahoo.de> (raw)
In-Reply-To: <announce.87o8h52pnz.fsf@Rainer.invalid>
Hi Achim,
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.
I haven't seen anything like this before the update.
Here are links to one failing and one good case:
Fail run package version:
https://github.com/coq/platform/runs/1803203762?check_suite_focus=true#step:4:164
Fail run error message:
https://github.com/coq/platform/runs/1803203762?check_suite_focus=true#step:4:1664
Good run package version:
https://github.com/coq/platform/runs/1799374171?check_suite_focus=true#step:4:164
I will revert to the old version of the package and see if the errors go
away.
The 32 bit version seems fine do far.
Best regards,
Michael
next prev parent reply other threads:[~2021-02-01 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 13:37 [ANNOUNCEMENT] Updated: binutils-2.35.2-1, mingw64-{i686, x86_64}-binutils-2.35.2-1 Achim Gratz
2021-02-01 9:25 ` Michael Soegtrop [this message]
2021-02-01 19:04 ` Random assembler errors after update mingw64-x86_64-binutils-2.35.2-1 Michael Soegtrop
2021-02-01 19:23 ` Achim Gratz
2021-02-01 20:17 ` Marco Atzeri
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=f4d1da5f-897f-0b81-f474-65725c8bf1df@yahoo.de \
--to=msoegtrop@yahoo.de \
--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).