-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port SpanHelpers.IndexOfAny(ref byte, byte, byte, int) to Vector128/256 #73384
Conversation
Tagging subscribers to this area: @dotnet/area-system-memory Issue Detailsx64On par. BenchmarkDotNet=v0.13.1.1828-nightly, OS=Windows 10 (10.0.18363.2212/1909/November2019Update/19H2)
Intel Xeon CPU E5-1650 v4 3.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET SDK=7.0.100-rc.1.22403.8
[Host] : .NET 7.0.0 (7.0.22.40210), X64 RyuJIT AVX2
LaunchCount=9
arm64BDN is reporting less than a nanosecond difference, which maps to 4%. On arm64 I don't have the tool that would allow me to verify whether it's caused by an alginment or codegen change. BenchmarkDotNet=v0.13.1.1828-nightly, OS=ubuntu 20.04
Unknown processor
.NET SDK=7.0.100-rc.1.22403.8
[Host] : .NET 7.0.0 (7.0.22.40210), Arm64 RyuJIT AdvSIMD
LaunchCount=9
|
WASM AOT compilation failed in this PR and is now failing on |
Submitting revert in #73476 |
@adamsitnik Please make sure to add links to the known issues tracking the failures when merging with red CI next time. |
x64
On par.
arm64
BDN is reporting less than a nanosecond difference, which maps to 4%. On arm64 I don't have the tool that would allow me to verify whether it's caused by an alginment or codegen change.
contributes to #64451