-
Notifications
You must be signed in to change notification settings - Fork 13
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
Move to LTS 10.0 #552
Comments
@capitanbatata I really like to move |
TorXakis builds with @capitanbatata I am curious to the performance with the new compiler! |
It depends on what we want. Right now |
Me too. I don't have my work computer, and I will get a different hardware anyway. @keremispirli will run the benchmarks for the current develop version, and @keremispirli and I are working on automating the benchmarks comparison process so that everyone can run them on his machine (since I don't think we'll get a cloud computer to run the benchmarks anyway). |
all tests seem to pass
|
@capitanbatata again strange benchmark values:
|
@pjljvandelaar No idea, that's what the criterion library is reporting. It might be related to issues haskell/criterion#65 and haskell/criterion#161. |
@PierreVDL @pjljvandelaar are you already working on bumping the LTS? I'm also working on it since you assigned the issue to me :/ ... |
And this is the issue related to the |
I only tested LTS 10.0, and found out it is valid for TorXakis. |
- Updated TorXakis to LTS-10.0 - Updated sqatt to LTS-10.0 - A `stack_appveyor` file was introduced to use the integer simple variant of GHC, which reduces build time. - Documented how to - The `stack` version is output in the build scripts (semaphore and appveyor). - The build script in appveyor now retries to build TorXakis (10 times) due to random failures in the stack build. - Removed the warnings by enabling the `MonoLocalBinds` extension. A more fundamental fix will require making `ValExpr` type safe. - Removed the extra deps using the newest features of stack (since 1.6.1). - Removed the mention to the use of `fast` flag, since now the optimizations are disabled (See pull request #539 ). - Added instructions on how to run the benchmarks. Fixes #552 Fixes #553
Move to LTS 10.0 (and stack 1.6.1)
Some warnings have to be fixed like
The text was updated successfully, but these errors were encountered: