CTFE optimsation: Remember when constfolding has been done #2570
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When an array literal or struct literal originated in CTFE, interpreting it again will have no effect. This gives a small speedup.
|
Please rebase. |
|
FYI, I can't see any improvement in any of the pathological cases I'm testing this on: Such as: bug 6498.
|
|
However I'm not discarding the fact that this information is useful. :) |
|
please rebase |
|
On closer inspection, this was implemented by #4627. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When an array literal or struct literal originated in CTFE, interpreting it again will have no effect.
Potentially this optimsation could have a large impact on compilation time, or may make almost no difference. Let's see,