From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Random assembler errors after update mingw64-x86_64-binutils-2.35.2-1
Date: Mon, 1 Feb 2021 21:17:03 +0100 [thread overview]
Message-ID: <57ebab4e-3034-dde4-0ff0-f8de82c0dcbc@gmail.com> (raw)
In-Reply-To: <f4d1da5f-897f-0b81-f474-65725c8bf1df@yahoo.de>
On 01.02.2021 10:25, Michael Soegtrop via Cygwin wrote:
> 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.
>
it can be a race that the current package is just exposing
> 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
513 File "kernel/nativelib.ml", line 1:
514 Error: Assembler error, input left in file
C:\cygwin_coq_platform\tmp\camlasm6b4377.s
515 make[1]: *** [Makefile.build:768: kernel/nativelib.cmx] Error 2
516 make[1]: Leaving directory
'/home/runneradmin/.opam/_coq-platform_.master/.opam-switch/build/coqide.dev'
a copy of the assembler file and original source could give some hint
prev parent reply other threads:[~2021-02-01 20:17 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 ` Random assembler errors after update mingw64-x86_64-binutils-2.35.2-1 Michael Soegtrop
2021-02-01 19:04 ` Michael Soegtrop
2021-02-01 19:23 ` Achim Gratz
2021-02-01 20:17 ` Marco Atzeri [this message]
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=57ebab4e-3034-dde4-0ff0-f8de82c0dcbc@gmail.com \
--to=marco.atzeri@gmail.com \
--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).