-
-
Notifications
You must be signed in to change notification settings - Fork 948
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
CoreRT support #718
Comments
adamsitnik
added a commit
that referenced
this issue
Apr 15, 2018
adamsitnik
added a commit
that referenced
this issue
Apr 15, 2018
adamsitnik
added a commit
that referenced
this issue
Apr 15, 2018
…renced projects, I removed them and referenced what we need as links, #718
adamsitnik
added a commit
that referenced
this issue
Apr 15, 2018
…e 2.1 to support MemoryDiagnoser ;), #718
adamsitnik
added a commit
that referenced
this issue
Apr 15, 2018
Merged
18 tasks
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
…renced projects, I removed them and referenced what we need as links, dotnet#718
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
…e 2.1 to support MemoryDiagnoser ;), dotnet#718
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
alinasmirnova
pushed a commit
to alinasmirnova/BenchmarkDotNet
that referenced
this issue
Sep 22, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BenchmarkDotNet supports CoreRT! However, you might want to know how it works to get a better understanding of the results that you get.
<TargetFramework>netcoreapp2.1</TargetFramework>
in the .csproj file)[CoreRtJob]
attribute or by using the fluent Job config APIJob.ShortRun.With(Runtime.CoreRT)
dotnet run -c Release -f netcoreapp2.1
) and BenchmarkDotNet does all the CoreRT compilation for you. If you want to check what files are generated you need to apply[KeepBenchmarkFiles]
attribute to the class which defines benchmarks.By default BenchmarkDotNet uses the latest version of
Microsoft.DotNet.ILCompiler
to build the CoreRT benchmark according to this instructions.Note: BenchmarkDotNet is going to run
dotnet restore
on the auto-generated project. The first time it does so, it's going to take a LOT of time to download all the dependencies (few minutes). Just give it some time and don't pressCtrl+C
too fast ;)If you want to benchmark some particular version of CoreRT you have to specify it in an explicit way:
Compiling source to native code using the ILCompiler you built
If you are an CoreRT contributor and you want to benchmark your local build of CoreRT you have to provide necessary info (IlcPath):
BenchmarkDotNet is going to follow these instructrions to get it working for you.
Using CPP Code Generator
If you want to test CPP Code Generator you have to use
UseCppCodeGenerator
method:Note: You might get some
The method or operation is not implemented.
errors as of today if the code that you are trying to benchmark is using some features that are not implemented by CoreRT/transpiler yet...Sample results:
The text was updated successfully, but these errors were encountered: