GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — GH-115457: Support splitting and replication of micro ops. by markshannon · Pull Request #115558 · python/cpython Conversation
|
|
Also, I like how clean this is in the DSL! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| else if (oparg < _PyUop_Replication[opcode]) { | ||
| buffer[pc].opcode = opcode + oparg + 1; | ||
| } | ||
| else if (opcode == _JUMP_TO_TOP || opcode == _EXIT_TRACE) { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Maybe use op_is_end here?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It's a static function in another file.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
We'll leave it up to Ken Jin to turn it into a macro or static inline in a header. (Because he's adding another opcode that could end the list of opcodes, a new JUMP variant.)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general, just one minor comment.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| properties=compute_properties(op), | ||
| ) | ||
| if effect_depends_on_oparg_1(op) and "split" in op.annotations: | ||
| result.properties.oparg_and_1 = True |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
For code consistency, shouldn't this be compute_properties?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't what be compute_properties?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Woops I meant shouldn't this be computed in compute_properties ?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
The oparg_and_1 property only applies to the base uop, not the replicas as their behavior does not depend on oparg & 1. compute_properties computes the properties from the definition only, so we would need to modify oparg_and_1 anyway.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Cool!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| else if (oparg < _PyUop_Replication[opcode]) { | ||
| buffer[pc].opcode = opcode + oparg + 1; | ||
| } | ||
| else if (opcode == _JUMP_TO_TOP || opcode == _EXIT_TRACE) { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
We'll leave it up to Ken Jin to turn it into a macro or static inline in a header. (Because he's adding another opcode that could end the list of opcodes, a new JUMP variant.)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
The refleaks buildbot failed on Edit: it's likely to be fixed in #115728 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.