Skip to content
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

Provide a set of performance tests over the new single-precision math APIs #6838

Closed
tannergooding opened this issue Oct 18, 2016 · 3 comments · Fixed by dotnet/coreclr#9354
Closed
Labels
tenet-performance Performance related issue
Milestone

Comments

@tannergooding
Copy link
Member

PR dotnet/coreclr#5492 implemented dotnet/corefx#1151, by providing scalar single-precision floating-point support for many of the trigonometric, logarithmic, and other common mathematical functions.

However, there is still the additional work that needs to be done to provide a full set performance tests over the new single-precision math APIs.

This work is partially blocked on dotnet/corefx#12183 being merged so that a proper NuGet package is available with the appropriate contract assembly.

@tannergooding
Copy link
Member Author

I am self-assigning these for the time being and am going to work on getting these completed.

@tannergooding tannergooding self-assigned this Oct 18, 2016
@tannergooding
Copy link
Member Author

This will be resolved with dotnet/coreclr#9354, once that is unblocked (the perf tests do not currently support projects that target netcoreapp).

@gkhanna79
Copy link
Member

CC @brianrob

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@tannergooding tannergooding removed their assignment May 26, 2020
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tenet-performance Performance related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants