Showing content from http://mail.python.org/pipermail/python-dev/attachments/20160201/04caf59b/attachment.html below:
<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, 1 Feb 2016 at 12:16 Yury Selivanov <<a href="mailto:yselivanov.ml@gmail.com">yselivanov.ml@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Brett,<br>
<br>
On 2016-02-01 3:08 PM, Brett Cannon wrote:<br>
><br>
><br>
> On Mon, 1 Feb 2016 at 11:51 Yury Selivanov <<a href="mailto:yselivanov.ml@gmail.com" target="_blank">yselivanov.ml@gmail.com</a><br>
> <mailto:<a href="mailto:yselivanov.ml@gmail.com" target="_blank">yselivanov.ml@gmail.com</a>>> wrote:<br>
><br>
>Â Â Â Hi Brett,<br>
><br>
[..]<br>
><br>
><br>
>Â Â Â The first two fields are used to make sure that we have objects of the<br>
>   same type. If it changes, we deoptimize the opcode immediately. Then<br>
>   we try the offset. If it's successful - we have a cache hit. If not,<br>
>Â Â Â that's fine, we'll try another few times before deoptimizing the<br>
>Â Â Â opcode.<br>
><br>
><br>
> So this is a third "next step" that has its own issue?<br>
<br>
It's all in issue <a href="http://bugs.python.org/issue26219" rel="noreferrer" target="_blank">http://bugs.python.org/issue26219</a> right now.<br>
<br>
My current plan is to implement LOAD_METHOD/CALL_METHOD (just opcodes,<br>
no cache) in 26110.<br>
<br>
Then implement caching for LOAD_METHOD, LOAD_GLOBAL, and LOAD_ATTR in<br>
26219. I'm flexible to break down 26219 in three separate issues if<br>
that helps the review process (but that would take more of my time):<br>
<br>
- implement support for opcode caching (general infrastructure) +<br>
LOAD_GLOBAL optimization<br>
- LOAD_METHOD optimization<br>
- LOAD_ATTR optimization<br></blockquote><div><br></div><div>I personally don't care how you break it down, just trying to keep all the moving pieces in my head. :)</div><div><br></div><div>Anyway, it sounds like PEP 509 is blocking part of it, but the LOAD_METHOD stuff can go in as-is. So are you truly blocked only on getting the latest version of that patch up to <a href="http://bugs.python.org/issue26110">http://bugs.python.org/issue26110</a> and getting a code review?</div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4