From: nobu.nokada@softhome.net
To: ruby-core@ruby-lang.org
Subject: Re: A truth? patch + benchmarks
Date: Mon, 5 Aug 2002 10:44:29 +0900 [thread overview]
Message-ID: <200208050144.g751i6g07965@sharui.nakada.kanuma.tochigi.jp> (raw)
In-Reply-To: <000001c23c1a$d864b4d0$0100a8c0@lony>
Hi,
At Mon, 5 Aug 2002 09:58:11 +0900,
Christoph wrote:
> If the ``magic'' is referring to my observed speedup of replacing
> most RTEST macro calls with an inlined function call (at least on
> my windows machine this effect seems to be real), I really have
> to pass (besides making uneducated guesses) but I tend to think that
> this "compilation optimization artifact" is wedded to the current
> implementation (putting things in perspective, changing from VC6 to
> VC7 has an even bigger impact on speed).
It's true with gcc 2.95.3 under i686-linux.
> Just been curious (and pushy;-). I counted 26 ``T_VALUES'' in ruby.h,
> so from my naive point of view it might be possible (after
> rearranging the ``T_VALUES'' a bit, eehm, <= 31) to free up the sixth
> bit as a false/true bit. Of course, I tried this and did not see any
> obvious ill effect (running ``make test'' and ``rubicon'' on cygwin)
> - I guess that's what they call wishful thinking;-).
The modification means that *all* extension libraries must be
recompiled. Particularly, many extensions use T_DATA which is
bigger than 31. I guess it shouldn't be until (at least) minor
version will change.
--
Nobu Nakada
next prev parent reply other threads:[~2002-08-05 1:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 15:02 [PATCH] object.c ruby.h (fwd) Robert Skarwecki
2002-07-24 16:51 ` Boolean class (Re: [PATCH] object.c ruby.h) Yukihiro Matsumoto
2002-07-24 19:50 ` [PATCH] object.c ruby.h (fwd) GOTO Kentaro
2002-07-24 20:05 ` Dave Thomas
2002-07-25 4:22 ` unifying nil and false (Re: [PATCH] object.c ruby.h) Yukihiro Matsumoto
2002-07-25 4:59 ` Dave Thomas
2002-07-25 6:46 ` Yukihiro Matsumoto
2002-07-25 11:06 ` [PATCH] object.c ruby.h (fwd) GOTO Kentaro
2002-07-25 13:20 ` Dave Thomas
2002-07-25 17:42 ` nobu.nokada
2002-07-25 17:55 ` Dave Thomas
2002-07-25 18:11 ` nobu.nokada
2002-07-25 18:28 ` Dave Thomas
2002-07-25 19:53 ` GOTO Kentaro
2002-07-25 20:34 ` Dave Thomas
2002-07-25 22:23 ` GOTO Kentaro
2002-07-27 8:04 ` Masaki Suketa
2002-07-27 12:40 ` Dave Thomas
2002-08-03 9:04 ` Masaki Suketa
2002-08-05 1:39 ` NAKAMURA, Hiroshi
2002-08-06 11:53 ` Masaki Suketa
2002-08-09 13:20 ` NAKAMURA, Hiroshi
2002-08-10 12:19 ` Masaki Suketa
2002-08-12 3:48 ` NAKAMURA, Hiroshi
2002-07-26 10:11 ` YANAGAWA Kazuhisa
2002-07-31 14:47 ` A truth? patch + benchmarks Christoph
2002-07-31 15:03 ` ts
2002-08-01 6:39 ` Christoph
2002-08-01 7:02 ` Yukihiro Matsumoto
2002-08-02 7:12 ` Christoph
2002-08-02 7:20 ` ts
2002-08-02 8:54 ` Christoph
2002-08-03 9:51 ` Yukihiro Matsumoto
2002-08-05 0:58 ` Christoph
2002-08-05 1:44 ` nobu.nokada [this message]
2002-08-16 6:52 ` Mswin32 build flags Christoph
2002-08-16 7:12 ` U.Nakamura
2002-09-03 18:51 ` Christoph
2002-07-26 1:16 ` [PATCH] object.c ruby.h (fwd) NAKAMURA, Hiroshi
2002-07-26 15:23 ` Michal Rokos
2002-07-26 15:31 ` Dave Thomas
2002-07-26 16:37 ` Yukihiro Matsumoto
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=200208050144.g751i6g07965@sharui.nakada.kanuma.tochigi.jp \
--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).