Implement longdouble as a wrapper around llvm::APFloat. #587
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Nice progress. Now we just need 2.065 in master. ;) |
|
So what's the next step here? Does this require 3.4/3.5? |
|
No, there should be no dependency on the LLVM version. Next step is to fill the missing pieces, test and merge. :-) |
This commit introduces a new class ldc::longdouble which provides real_t semantics based on the target. It uses llvm::APFloat as base implementation. This fixes issue ldc-developers#259.
redstar
pushed a commit
that referenced
this pull request
Sep 27, 2014
reuse rt_init/rt_term in main
redstar
pushed a commit
that referenced
this pull request
Sep 27, 2014
reuse rt_init/rt_term in main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a new class ldc::longdouble which provides real_t
semantics based on the target. It uses llvm::APFloat as base implementation.
This fixes issue #259.