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

the two build systems should build the same versions of programs and libraries #1243

Closed
DanGrayson opened this issue Jun 5, 2020 · 5 comments · Fixed by #1453
Closed

the two build systems should build the same versions of programs and libraries #1243

DanGrayson opened this issue Jun 5, 2020 · 5 comments · Fixed by #1453
Labels
build issue platform specific issues involving compiling M2, generating examples, or running tests

Comments

@DanGrayson
Copy link
Member

It would be a good idea to keep the versions in sync, for then examples and tests that work under one build system will be more likely to work under the other.

Originally posted by @DanGrayson in #1239 (comment)

@mikestillman
Copy link
Member

In particular, the basic defaults should be the same: either both should use mpir, or both use gmp.

@mahrud
Copy link
Member

mahrud commented Jun 11, 2020

Are there recent benchmarks of which is faster? I know Sage uses mpir by default and I believe @dimpase had thoughts on this.

@dimpase
Copy link
Contributor

dimpase commented Jun 11, 2020

Sage's current default is to use a system-wide GMP installation (it can actually be MPIR in GMP-compatible mode), and nudge the user to install GMP if it's not installed (by printing a message to this effect at the end of ./configure's run).

My understanding is that MPIR's development is mostly on hold, since appearance of Meltdown and Spectre attack on Intel CPUs, rendering efforts to optimise MPIR's assembly routines (something that made them faster than GMP) problematic, as it was assumed that extensive CPU's patching needed to mitigate against these attacks would break them.

I don't know whether this prediction came to be true, perhaps @wbhart can comment.

@mahrud
Copy link
Member

mahrud commented Jun 14, 2020

Referencing #475, which is about using OpenBLAS. The CMake build uses OpenBLAS if it is present.

@mahrud mahrud added the build issue platform specific issues involving compiling M2, generating examples, or running tests label Aug 1, 2020
@mahrud
Copy link
Member

mahrud commented Aug 4, 2020

@DanGrayson #475 is still remaining.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build issue platform specific issues involving compiling M2, generating examples, or running tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants