Thomas Morley - 46 minutes ago
Inline assembler fallback for _FPU_SETCW() missing in MINGW libraries
Issue 4943
As Issue 4943 on Windows compilation was triggered by
missing _FPU_SETCW() in the MINGW libraries, an alternate call to
initiate the X87 FPU setup as an inline-assembler command is added
- for MINGW 32 Bit compilation only.
https://codereview.appspot.com/575600043/
On Sat, 9 Jan 2016 at 09:55 Chris Yate chrisyate@gmail.com wrote:
So, it turns out this was easy to minimise the code. File is attached.
It's still ~70 bars but only one voice, which is the dynamics staff of a
piano score (without anything else), so it's only silent music."AutoPageBreaksOff" in the score block causes the exception failure.
I note some "insane spring distance" warnings.These don't happen in the
real thing.Chris
Note: According to Phil H's own tests: "This started in 2.19.21. 2.19.20 is OK."
Update: an instance of this affects also non-Windows systems, see comment below.
Error reproduced by James L on Windows 8.1 - screenshot of error attached.
Does not occur in Linux builds.
Pretty sure that "This started in 2.19.21. 2.19.20 is OK." is a red herring since 2.19.21 was the version where assertions were enabled for more than just --disable-optimising.
So I'll assume that the error is older than that. Probably lots older.
I see the same assertion failure on OSX 10.8.5
Here's a tiny example that shows the problem.
The assertion failure is triggered with 18 bars (in both 6/8 and 4/4 time) but not with 17.
Last edit: Trevor Daniels 2017-01-06
Arrgh.
I misclicked and deleted the attachment.
Can it be restored?
Fortunately I created a backup a couple of weeks ago, so yes it can. It should be back in its proper place now.
Great. Thank tons.
Would it be possible to configure the settings that only the author and admins (you and Phil) can delete?
Thomas Morley wrote Friday, January 06, 2017 6:50 PM
No problem - lucky I took a year-end backup though!
I don't think so. Deletion seems to be part of Update permissions, which all Devs and Members have. Does seem rather surprising though.
Trevor
And I confirm that the assertion failure does not happen on LilyDev.
A similar crash has been reported on -user-fr, which I was able to trim down to the minimal example below (commenting any line solves the bug). Interestingly though, this one’s reproducible even on GNU/Linux. (Whereas the previous snippets in this ticket aren’t.)
Here’s the log on GNU/Linux:
See also the attached Windows screenshot, which looks a lot like what had previously been reported. (Except it appears to be a different assertion.)
Last edit: Valentin Villenave 2019-01-10
Diff:
Some findings by Arnold can be found at:
http://lilypond.1069038.n5.nabble.com/Issue-4934-analysis-indicates-new-issue-td224851.html
regrettable there is a typo: 4934 <-> 4943 in his post.
I'll quote it here entirely:
Inline assembler fallback for _FPU_SETCW() missing in MINGW libraries
Issue 4943
As Issue 4943 on Windows compilation was triggered by
missing _FPU_SETCW() in the MINGW libraries, an alternate call to
initiate the X87 FPU setup as an inline-assembler command is added
- for MINGW 32 Bit compilation only.
http://codereview.appspot.com/577450043
Diff:
Passes make, make check and a full make doc.
Patch on countdown for Feb 2nd
Patch on countdown for Feb 2nd
Inline assembler fallback for _FPU_SETCW() missing in x86 platforms
Issue 4943
As Issue 4943 on x86 platform compilations was triggered by
missing _FPU_SETCW(), an alternate call to initiate the
X87 FPU setup as an inline-assembler command is added.
http://codereview.appspot.com/575600043
New patch at
https://codereview.appspot.com/575600043/