Tier 2 optimizer: refactor to reuse constant symbols
未关闭
@Fidget-Spinner 已经在做这个了。
开始于 2024年6月11日。
performance
type-feature
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 35.9k
- 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
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。