-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Extract `fgMergeBlockReturn`. Morph is already a very vague verb in the Jit, try to use a more precise one. * Add a function header. * Make `compCurBB` available for `fgMorphBlockReturn`. When we generate an assignment we could need to create a new assertion, that requires `compCurBB` to be available. * Delete `INVALID_POINTER_VALUE`. I would like to remove it because: 1) it was debug only; 2) there were no null checks for `compHndBBtab`, because it is a dependent variable so there was no need to distinguish valid null pointer from a bad invalid pointer; 3) that is the only place where this mechanism was used. * Allow to CSE the merge return ASG. I can't see a reason why it should not, there are no diffs. The issue with the previous version was that we did not actually know what we were marking: GT_ASG, GT_COMMA, something else? Was the idea to mark individual ASG under COMMA?
- Loading branch information
Sergey Andreenko
authored
Mar 31, 2020
1 parent
162595e
commit c7a1ef6
Showing
4 changed files
with
120 additions
and
120 deletions.
There are no files selected for viewing
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
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
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
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