From: "nagachika (Tomoyuki Chikanaga)" <nagachika00@...>
Date: 2013-08-31T22:44:46+09:00
Subject: [ruby-core:56942] [ruby-trunk - Bug #8847] opt_regexpmatch2 does	not use method caching


Issue #8847 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 1.9.3: UNKNOWN, 2.0.0: REQUIRED to 1.9.3: UNKNOWN, 2.0.0: DONTNEED

Ah! I was misunderstanding that this is a bug fix.
Sorry for bother you.

----------------------------------------
Bug #8847: opt_regexpmatch2 does not use method caching
https://bugs.ruby-lang.org/issues/8847#change-41500

Author: charliesome (Charlie Somerville)
Status: Closed
Priority: Normal
Assignee: charliesome (Charlie Somerville)
Category: 
Target version: 
ruby -v: ruby 2.1.0dev (2013-08-31 trunk 42741) [x86_64-darwin12.4.0]
Backport: 1.9.3: UNKNOWN, 2.0.0: DONTNEED


The opt_regexpmatch2 instruction does not use method caching, instead it uses rb_funcall internally.

opt_regexpmatch2 is emitted by the compiler when a literal regexp is on the right hand side of the =~ operator.

This means a full method lookup must be performed every time the receiver of the =~ method call is not a String.


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