Skip to content

Upgrade libm and make no-std config testable #241

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

Merged
merged 8 commits into from
Nov 30, 2020

Conversation

brson
Copy link
Contributor

@brson brson commented Nov 29, 2020

Just looking for something to hack on I found #240 and decided to give it a try.

Along they way I needed to address a few other things, so they are all included here:

  • Make the --no-default-features --features=core configuration testable. This mostly involves manually importing std into test modules.
    • One ugly part here is that I had to add some cfgs to the example program so that it works with or without the 'std' config.
  • Add the core testing configuration to CI.
  • Change the way vec_bytebuf was constructing itself so that it passes the test suite fast
  • Restructure how the functions in libm are called since that library no longer includes the traits that were being used.

I can't verify that the libm panicking bug is actually fixed since it doesn't seem to be triggered by the test suite.

`vec![0; len]` uses a specialized intrinsic codepath, which, at least in debug
mode, is extremely faster than `resize`.

This makes the `alloc` test pass instantaneously instead of taking minutes.

Signed-off-by: Brian Anderson <[email protected]>
Signed-off-by: Brian Anderson <[email protected]>
These no longer exist in the latest revision of libm.

Signed-off-by: Brian Anderson <[email protected]>
Fixes wasmi-labs#240

Signed-off-by: Brian Anderson <[email protected]>
Signed-off-by: Brian Anderson <[email protected]>
@pepyakin
Copy link
Collaborator

Thanks!

I can't verify that the libm panicking bug is actually fixed since it doesn't seem to be triggered by the test suite.

Unfortunately, FWIW, I've never bumped into this bug. Still I am up for merging this, so hopefully this issue is resolved.

@pepyakin pepyakin merged commit e6134c7 into wasmi-labs:master Nov 30, 2020
@Robbepop Robbepop mentioned this pull request Sep 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants