https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112014-09-12T03:10:54ZRuby Issue Tracking SystemRuby master - Bug #10232: Trivial change of IMMEDIATE VALUE bits layouthttps://bugs.ruby-lang.org/issues/10232?journal_id=488612014-09-12T03:10:54Znormalperson (Eric Wong)normalperson@yhbt.net
<ul></ul><p><a href="mailto:ko1@atdot.net" class="email">ko1@atdot.net</a> wrote:</p>
<blockquote>
<p>(1) can be incompatibility issue so that I don't propose this fix strongly.<br>
Interpreter core doesn't depends on this spec, but C-exts can be affected.</p>
</blockquote>
<p>I think the only thing I've seen C-exts depend on is Qfalse == 0<br>
(which this preserves)</p>
<blockquote>
<p>Strange thing is: vm1_const</p>
</blockquote>
<p>I suspect this is CPU-specific behaviors. I cannot see the difference<br>
on my AMD FX-8320 (on vm1_const, haven't tested others)</p> Ruby master - Bug #10232: Trivial change of IMMEDIATE VALUE bits layouthttps://bugs.ruby-lang.org/issues/10232?journal_id=488622014-09-12T03:31:56Zko1 (Koichi Sasada)
<ul></ul><p>Eric Wong wrote:</p>
<blockquote>
<blockquote>
<p>Strange thing is: vm1_const</p>
</blockquote>
<p>I suspect this is CPU-specific behaviors. I cannot see the difference<br>
on my AMD FX-8320 (on vm1_const, haven't tested others)</p>
</blockquote>
<p>I agree.</p> Ruby master - Bug #10232: Trivial change of IMMEDIATE VALUE bits layouthttps://bugs.ruby-lang.org/issues/10232?journal_id=501372014-11-27T11:28:14Zko1 (Koichi Sasada)
<ul><li><strong>Target version</strong> changed from <i>2.2.0</i> to <i>2.6</i></li></ul> Ruby master - Bug #10232: Trivial change of IMMEDIATE VALUE bits layouthttps://bugs.ruby-lang.org/issues/10232?journal_id=628752017-02-06T02:55:52Zko1 (Koichi Sasada)
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Rejected</i></li></ul><p>Reject it and revisit sometime.</p>