The runtime was handling the message lookup correctly in this case, but only as a side-effect of the fallback code from when type-dependent dispatch is not possible. This resulted in a confusing warning message, telling you that you were calling a method with an incorrect signature, when the two signatures that it printed were the same.
This case is now handled correctly, so the warning disappears (unless you really are calling a method with the wrong signature and have TDD enabled).
Removed GNU dtable and sparse array implementations, replaced entirely now with versions based on the Étoilé runtime. Performance is roughly equivalent in microbenchmarks, memory usage is significantly lower (Gorm goes from 95MB to 50MB on my machine - this will be even more pronounced on 64-bit systems), which should improve cache usage considerably. Still room for some performance tuning, however.
I now have an out-of-tree replacement for the dtable stuff, so sarray.{h,c} will be going away soon. The replacement offers similar (slightly worse currently) performance in microbenchmarks, but uses half as much memory (Gorm goes from 95MB to 48MB on my machine). This will be committed once it's been tweaked a little bit.
- nil_method now returns 0, not receiver.
- Metaclasses actually get their dtables installed with the new ABI. For some reason this wasn't being done, so class messages didn't work with the new ABI. Now they do and (at least some) nontrivial programs work.
- Undid commenting out of the code setting the fast ivar access pointers. I can't remember why this was commented out, but it seems not to break anything. I have an LLVM pass that makes compiled code access these pointers, but it's not committed yet.
theraven
rfm