Change default opt-level for Config to speed. - #988
Conversation
|
Looking into the various test failures. |
|
Looks like some of the SIMD spec testsuite tests are failing when optimizing for speed: |
|
Want to update the wast testsuites with a FIXME where we set the optimization level to none, but only for the simd tests? |
|
Can do. Pinging @abrown relating to the SIMD failures when we optimize for speed. Looks like there are additional failures for trap-related tests on Windows that I'll investigate, possibly related to unwind. |
|
For posterity, here's one such SIMD failure: |
|
The SIMD tests are the only ones that failing but I am seeing a bunch of additional panic output during the test executions: |
|
@peterhuene, thanks for the heads up. I suspect this is related to bytecodealliance/cranelift#1388 (using REX prefixes to access more registers) but I'm not exactly sure I understand what the effects of |
|
The |
|
@abrown thanks for looking into it! I'll disable optimization for the tests for now. |
This commit changes the default opt-level for a new `Config` to `speed`. Fixes bytecodealliance#981.
d6252bc to
6c6bae7
Compare
6c6bae7 to
9ffa19c
Compare
|
I've opened bytecodealliance/cranelift#1409 to track the SIMD issue. |
This PR changes the default opt-level for a new
Configtospeed.Fixes #981.