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

Fix for linker errors from multiprecision changes. #735

Merged
merged 1 commit into from
Jan 8, 2022
Merged

Conversation

jzmaddock
Copy link
Collaborator

Fixes #733.

@ckormanyos
Copy link
Member

Nice!

Just to be sure... So MSVC build(s) simply remain unchanged, right? And do not erroneously try to use 128-bit artifacts either?

@jzmaddock
Copy link
Collaborator Author

Just to be sure... So MSVC build(s) simply remain unchanged, right? And do not erroneously try to use 128-bit artifacts either?

Correct. You only hit this if __float128 is an available type, and your precision is < 113 bits: in which case you should probably be using __float128 in the first place.

@jzmaddock
Copy link
Collaborator Author

Failures are CI SNAFU's, merging...

@jzmaddock jzmaddock merged commit 82b595a into develop Jan 8, 2022
@NAThompson NAThompson deleted the issue733 branch January 8, 2022 17:02
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.

boost::multiprecision linker errors
2 participants