[#79914] [Ruby trunk Bug#13282] opt_str_freeze does not always dedupe — normalperson@...
Issue #13282 has been reported by Eric Wong.
4 messages
2017/03/05
[#80140] [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus) — shyouhei@...
Issue #13295 has been updated by shyouhei (Shyouhei Urabe).
5 messages
2017/03/13
[#80362] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— Eric Wong <normalperson@...>
2017/03/26
shyouhei@ruby-lang.org wrote:
[#80368] Re: [Ruby trunk Feature#13295] [PATCH] compile.c: apply opt_str_freeze to String#-@ (uminus)
— SASADA Koichi <ko1@...>
2017/03/27
On 2017/03/26 15:16, Eric Wong wrote:
[#80205] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint — Eric Wong <normalperson@...>
duerst@ruby-lang.org wrote:
4 messages
2017/03/17
[#80213] Re: [ruby-cvs:65166] duerst:r58000 (trunk): clarifiy 'codepoint' in documentation of String#each_codepoint
— Martin J. Dürst <duerst@...>
2017/03/17
Hello Eric,
[#80290] [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch — normalperson@...
Issue #13355 has been reported by normalperson (Eric Wong).
4 messages
2017/03/23
[#80410] Re: [Ruby trunk Feature#13355] [PATCH] compile.c: optimize literal String range in case/when dispatch
— Eric Wong <normalperson@...>
2017/03/27
normalperson@yhbt.net wrote:
[#80415] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
5 messages
2017/03/28
[#80488] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
4 messages
2017/03/29
[ruby-core:80070] [Ruby trunk Bug#13279] Math.log10 accuracy regression
From:
naruse@...
Date:
2017-03-12 17:24:56 UTC
List:
ruby-core #80070
Issue #13279 has been updated by Yui NARUSE. Backport changed from 2.2: DONTNEED, 2.3: DONTNEED, 2.4: REQUIRED to 2.2: DONTNEED, 2.3: DONTNEED, 2.4: DONE ruby_2_4 r57928 merged revision(s) 57778,57779. ---------------------------------------- Bug #13279: Math.log10 accuracy regression https://bugs.ruby-lang.org/issues/13279#change-63499 * Author: Javier Goizueta * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.2: DONTNEED, 2.3: DONTNEED, 2.4: DONE ---------------------------------------- I've notice a degradation in the precision of Math.log10 in Ruby 2.4 with respect to 2.1: ~~~ 2.1.2 :136 > Math.log10 10**1000 => 1000.0 2.4.0 :009 > Math.log10 10**1000 => 999.9999999999999 ~~~ The problem has been introduced in this commit: git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@55641 b2dd03c8-39d4-4d8f-98ff-823fe69b080e (https://github.com/ruby/ruby/commit/fd2c613b1cec46d0b02df722bb00ae01154d5dc3) The use of arithmetic to compute the log10(2) introduces some roundoff error in that constant: ~~~ 2.1.2 :140 > M_LN2 = 0.693147180559945309417232121458176568 => 0.6931471805599453 2.1.2 :141 > M_LN10 = 2.30258509299404568401799145468436421 => 2.302585092994046 2.1.2 :142 > l2 == M_LN2/M_LN10 => false 2.1.2 :144 > l2 => 0.3010299956639812 2.1.2 :145 > M_LN2/M_LN10 => 0.30102999566398114 ~~~ * The correct value of the constant (base-10 log of 2) is 0.301029995663981195213738894724... * The log10(2) function yields a correctly rounded approximation of 0.3010299956639812 * But the computed division of constants results in 0.30102999566398114 -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>