-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: add optimization phase #1047
base: main
Are you sure you want to change the base?
Changes from 12 commits
bf955e7
b297ab2
50af1d5
c5d8678
e9f02f5
34b82b6
90bcde3
39ce816
d0e55d7
274182e
0c47ed9
c9e02f3
deb9e74
d9e7549
e33d97e
21578bc
9fb7586
4ee15ce
d60dd12
270b867
f859692
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -51,6 +51,16 @@ | |||||
"default": false, | ||||||
"description": "False by default. If set to true, enables generation of a getter the information on the interfaces provided by the contract.\n\nRead more about supported interfaces: https://docs.tact-lang.org/ref/evolution/OTP-001." | ||||||
}, | ||||||
"skipTactOptimizationPhase": { | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Renaming it to skipPartialEval would imply that the optimization phase only includes partial evaluation, but it will also include other steps, like constant propagation in the future (and probably other techniques as well). Is there a way to keep the "skipTactOptimizationPhase" for the entire phase, but to include sub-options for each of the steps in the optimization phase? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We need to come up with a plan for those optimizations and design a config for those then There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess it is enough to have an option for each step inside the optimization phase and avoid the complication of having an option for the entire phase. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yeah. All right. I will change the option to skipPartialEval, and once we have a plan, I will carry out the changes in a separate issue/PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll open an issue-task regarding this. |
||||||
"type": "boolean", | ||||||
"default": false, | ||||||
"description": "False by default. If set to true, skips the Tact code optimization phase." | ||||||
}, | ||||||
"dumpCodeBeforeAndAfterTactOptimizationPhase": { | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This needs to be split into two options, |
||||||
"type": "boolean", | ||||||
"default": false, | ||||||
"description": "False by default. If set to true, dumps the code produced before and after the Tact code optimization phase." | ||||||
}, | ||||||
"experimental": { | ||||||
"type": "object", | ||||||
"description": "Experimental options that might be removed in the future. Use with caution!", | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
irrelevant change