SpanHelpers.IndexOf picks the correct overload for SequenceEqual #1113
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.
In
runtime/src/libraries/System.Private.CoreLib/src/System/SpanHelpers.Byte.cs
Line 52 in 8c0a1d9
for
SequenceEqualthe generic non-vectorized overloadruntime/src/libraries/System.Private.CoreLib/src/System/SpanHelpers.T.cs
Line 778 in 8c0a1d9
get picked, thus resulting in correct code but slower than intended code.
This PR makes a mini change so that the correct optimized overload get chosen
runtime/src/libraries/System.Private.CoreLib/src/System/SpanHelpers.Byte.cs
Line 1313 in 8c0a1d9
Same applies to
LastIndexOf.I stumbled acrros this while investigating a "strange perf problem" (as it turned out this was the cause).
A simple repro shows the problem, in which
IndexOfis just re-implemented (copied) so that the correct overload is taken.Repro code
This results in
From PerfView before this change (i.e.


Defaultfrom the repro)and with this PR (i.e.
Selffrom the repro)