Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

[No Merge]Adding SSE4.2 STTNI intrinsic APIs #19958

Closed
wants to merge 1 commit into from

Conversation

fiigii
Copy link

@fiigii fiigii commented Sep 14, 2018

This PR adds SSE4.2 STTNI intrinsic APIs that need to be reviewed.

@fiigii
Copy link
Author

fiigii commented Sep 14, 2018

@CarolEidt @tannergooding @eerhardt PTAL

@4creators
Copy link

Could we simplify enum names? IndexStringComparisonMode.NegativeUsefulResult is a bit large and not very much self documenting name.

Copy link

@CarolEidt CarolEidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should have a "Redesign" PR in coreclr.
I think we should first discuss the kinds of design decisions we're talking about in the corefx issue (https://github.com/dotnet/corefx/issues/30373)

/// PCMPISTRI xmm, xmm/m128, imm8
/// int _mm_cmpistrs (__m128i a, __m128i b, const int imm8)
/// </summary>
public static bool CompareNoMatchAndRightNotTerminated(Vector128<sbyte> left, Vector128<sbyte> right, StringComparisonMode mode) { throw new PlatformNotSupportedException(); }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so verbose - since we have RightTerminated doesn't it make sense for the lack of that modifier to imply that it is not right terminated?
Also, could we think of a better way to express CompareNoMatch?

@fiigii fiigii changed the title Redesign SSE4.2 STTNI intrinsic APIs [No Merge]Adding SSE4.2 STTNI intrinsic APIs Nov 12, 2018
@tannergooding
Copy link
Member

@fiigii, can this be closed for now; until we have a better design?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants