From: luislavena@...
Date: 2014-08-25T01:08:19+00:00
Subject: [ruby-core:64539] [ruby-trunk - Bug #10120] TestSprintf#test_float	still an issue

Issue #10120 has been updated by Luis Lavena.

Assignee set to Nobuyoshi Nakada

Hello,

Now after r47129, mingw-w64 is failing again, so we are back to the beginning.

~~~
ruby -v: ruby 2.2.0dev (2014-08-24 trunk 47266) [i386-mingw32]
TestSprintf#test_float [C:/Users/Luis/Code/ruby/ruby/test/ruby/test_sprintf.rb:208]:
[ruby-dev:42551].
<"0x1p+2"> expected but was
<"0x1p+1">.
~~~

I'm out of ideas on how to solve this without: force SSE or change the pow/float implementation for MinGW.

Open to suggestions.

Thank you.


----------------------------------------
Bug #10120:  TestSprintf#test_float still an issue
https://bugs.ruby-lang.org/issues/10120#change-48468

* Author: Vit Ondruch
* Status: Feedback
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: 
* Target version: 
* ruby -v: ruby 2.0.0p353 (2013-11-22 revision 43784) [i686-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The fix for #8358 is build time solution. Unfortunately it turns out that this does not work so well for for distributions such as Fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=1101811

The issues is that the SSE2 support is determined during build time, i.e. if builder supports SSE2, then the instructions are enabled. However, later when the packaged Ruby is executed on platform which does not support SSE2, it may result in issues as described in the above mentioned ticket.

Is there some way, how to resolve this issue in runtime rather than build time?



-- 
https://bugs.ruby-lang.org/