From: Eric Wong <normalperson@yhbt.net>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:64985] Re: [ruby-trunk - Bug #10232] [Open] Trivial change of IMMEDIATE VALUE bits layout
Date: Fri, 12 Sep 2014 02:59:48 +0000 [thread overview]
Message-ID: <20140912025948.GA6413@dcvr.yhbt.net> (raw)
In-Reply-To: <redmine.issue-10232.20140912012732.0e9e499bf28f46d5@ruby-lang.org>
ko1@atdot.net wrote:
> (1) can be incompatibility issue so that I don't propose this fix strongly.
> Interpreter core doesn't depends on this spec, but C-exts can be affected.
I think the only thing I've seen C-exts depend on is Qfalse == 0
(which this preserves)
> Strange thing is: vm1_const
I suspect this is CPU-specific behaviors. I cannot see the difference
on my AMD FX-8320 (on vm1_const, haven't tested others)
next prev parent reply other threads:[~2014-09-12 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-10232.20140912012732@ruby-lang.org>
2014-09-12 1:27 ` [ruby-core:64979] [ruby-trunk - Bug #10232] [Open] Trivial change of IMMEDIATE VALUE bits layout ko1
2014-09-12 2:59 ` Eric Wong [this message]
2014-09-12 3:10 ` [ruby-core:64986] [ruby-trunk - Bug #10232] " normalperson
2014-09-12 3:31 ` [ruby-core:64987] " ko1
2014-11-27 11:28 ` [ruby-core:66522] " ko1
2017-02-06 2:55 ` [ruby-core:79444] [Ruby trunk Bug#10232][Rejected] " ko1
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140912025948.GA6413@dcvr.yhbt.net \
--to=ruby-core@ruby-lang.org \
/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).