You could probably use MS's NGen or Mono's
--full-aot / --aot=full flag to compile it to a native build. I expect that would bump up the hashes a bit.
That would actually worsen performance. All AOT does is perform the bytecode-to-native translation ahead of time. The JIT-compiler will perform the same process at runtime when each method is first entered -- so this step only happens once per method for each instance of the program.
The difference is that the JIT knows what CPU it is running on and can use optimizations specific to the features your CPU has. Since AOT code is designed to be distributed with the corresponding assembly, the AOT-compiler has to assume a generic CPU and so it will create compatible but slower code.
Well, if all you did was compile from source for your miner, you could add the -O=all flag. Then again, the documentation says generics suck on AOT so I guess you could profile the AOT vs non-AOT and see how the milage varies.
Are you going to support any of the new parallelism / async stuff? If so, I wouldn't mind getting in this just to try the new sexiness out
Show Posts
) 
