Allow Value Propagation to remove TR::new that creates a value type instance #7239
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.
Previously, value type instances created with the jitNewObject helper in a
TR::new
operation would result in anInstantiationError
. That prevented Value Propagation from removing aTR::new
operation that was known to create an instance of a value type. This change prepares for the possibility that aTR::new
with ajitNewObject
helper could be used to create an instance of a value type, which means the operation need not be kept just to allow for anInstantiationError
to be thrown.Whether a
TR::new
withjitNewObject
can be used to create a value type instance is indicated by the method ObjectModel methodOMR::ObjectModel::areValueTypeInstancesCreatedWithBCNew
. The default implementation returns false, but downstream uses might override that implementation.This pull request will require a co-ordinated merge with OpenJ9 pull request eclipse-openj9/openj9#18790