fix(vmgen): string literal changing at run-time #1296
Merged
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.
Summary
Fix a string literal's underlying storage being modified when passing
a string literal to a
sink string
parameter, where the parameter ismodified within the callee. Only the VM backend was affected.
Details
No copy of the string literal (which was lifted into a constant
earlier) is created for string literals passed to
sink
parameters.This is not a problem for the C (copy-on-write strings are used) and
JS backend (a new run-time string instance is created on each string
literal usage), but it is for the VM backend.
Without a copy, the callee can directly modify the constant string's
underlying character storage, affecting all string literal usage
throughout the program.
mirgen
should introduce an intermediate temporary for the argument inthis case, but - at the moment - doing so would lead to worse code
generation for all code generators, so the problem is worked around in
vmgen
, by creating a copy of the string constant when passed to asink string
parameter.