Skip to content
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

salsa20: add #![no_std] directive #18

Merged
merged 1 commit into from Jul 30, 2019
Merged

salsa20: add #![no_std] directive #18

merged 1 commit into from Jul 30, 2019

Conversation

tarcieri
Copy link
Member

No description provided.

@newpavlov
Copy link
Member

Maybe also add CI test for no_std build?

@tarcieri
Copy link
Member Author

Did this quickly through the GitHub web UI... will pull this branch down and test all of these crates on no_std (e.g. thumbv6) and WASM targets.

@newpavlov newpavlov merged commit 510d484 into master Jul 30, 2019
tarcieri added a commit that referenced this pull request Aug 12, 2019
This uses a CI config more like the one at:

https://github.com/RustCrypt/signatures

It runs all tests with the `--release` flag to ensure that crates aren't
broken by release-dependent functionality after being tested in debug
mode (we can add back debug mode testing if it's helpful, but it doesn't
look like we have anything presently gated on debug builds). I now see
@newpavlov also requested it on #20.

It also tests on a `no_std` platform (thumbv7) which @newpavlov
requested in #18.

Finally, it tests with `--all-features`. This should uncover some
lingering breakages (it won't in this commit, but it appears some of the
conditional compilation is incorrectly gated and I intend to fix it in a
follow-up commit).
@tarcieri tarcieri deleted the salsa20/no_std branch August 19, 2019 19:55
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.

None yet

2 participants