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.

Sign up for GitHub

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

Jump to bottom

Improve platform testing, especially for AVX2-specific (and similar) code #131

Open
briansmith opened this issue Feb 29, 2016 · 6 comments
Open

Improve platform testing, especially for AVX2-specific (and similar) code #131

briansmith opened this issue Feb 29, 2016 · 6 comments
Labels
test-coverage

Comments

@briansmith
Copy link
Owner

Travis CI and the Linux VMs I use don't support AVX2 and/or other important features, so that code isn't getting tested thoroughly enough. In addition, currently the implementation is selected based on what the current CPU supports, which means that we never test some fallback implementations that are used when the CPU supports less than what Travis CI supports. We need to test every code path. This may require refactoring how implementations are chosen.
@briansmith briansmith mentioned this issue Feb 29, 2016
Closed
5 tasks
@briansmith
Copy link
Owner Author

See also https://bugs.chromium.org/p/chromium/issues/detail?id=434935

@briansmith
Copy link
Owner Author

The BoringSSL bug is now https://bugs.chromium.org/p/chromium/issues/detail?id=590332

@briansmith
Copy link
Owner Author

See also https://boringssl.googlesource.com/boringssl/+/6ce93ccb8087109a9c1444746402fcae1b12867a

@briansmith
Copy link
Owner Author

See also https://boringssl.googlesource.com/boringssl/+/54efa1afc08069c9dff3e7c419cea95222e65211

@briansmith
Copy link
Owner Author

See also https://boringssl.googlesource.com/boringssl/+/a6a049a6fb51a052347611d41583a0622bc89d60%5E%21/#F0

@briansmith
Copy link
Owner Author

See also https://boringssl.googlesource.com/boringssl/+/a6a049a6fb51a052347611d41583a0622bc89d60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
test-coverage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@briansmith