[TypeProf][ICP]Tweak max number of vtables in cost-benefit analysis #105620
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.
The ICP pass compares the vtable pointer with vtable address point for more efficient comparison sequence. The baseline is to compare the function pointer (loaded from vtable) with function address. The current cost-benefit analysis allows at most one vtable for each function candidate (to not insert instructions on hot paths).
icmp vtable-from-obj, getelementptr inbounds (i8, ptr @Derived2, i32 <constant-offset>)
compares vtable loaded from object with a vtable address point offset. After lowering, its size cost depends on whethergetelementptr inbounds (i8, ptr @Derived2, i32 <constant-offset>
can be folded into the icmp instruction.