-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Change default opt-level for Config to speed
.
#988
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
Config
tospeed
.Fixes #981.