python / python/cpython

Tier 2 optimizer: refactor to reuse constant symbols

未關閉
#120,325 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@Fidget-Spinner 已經在處理了。

開始於 2024年6月11日。

performance type-feature
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

Feature or enhancement

Proposal:

Right now the optimizer loses information across constant values. Say for example

def test_propagate_constants_sources(self):
    def thing(unused):
        x = 0
        for _ in range(100):
            x = 1
            y = Foo.attr + Foo.attr
            # Type information of `Foo_attr` is not propagated to here.
            z = Foo.attr + Foo.attr
        return x
    
    class Foo:
        attr = 1

    res, ex = self._run_with_optimizer(thing, 1)
    opnames = list(iter_opnames(ex))
    self.assertIsNotNone(ex)
    guard_type_version_count = opnames.count("_GUARD_BOTH_INT")
    # Test fails, because we insert 2 type guards instead of 1 (ie type information is not propagated, and guards are repeated)
    self.assertEqual(guard_type_version_count, 1)

After we promote Foo.attr to constants, we don't keep source information, so we don't keep track that the first Foo.attr is the same as the subsequent ones. Then LOAD_CONST_INLINE loads a brand new constant symbol each time, with no information.

https://github.com/python/cpython/blob/main/Python/optimizer_bytecodes.c#L422

A possible solution would be to keep some sort of ID for all constant promotions around.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。