Remove lightud 47-bit limit tests #9
Closed
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
LuaJIT now supports full 64-bit range light user data, or at least it claims to do; computations around the lightud(2^60) range seem to give an incorrect result with tostring().
|
Updated the tests to actually test larger values. It looks like lightud(2^60-42) onwards doesn't give the correct result but at the same time, pcall() also does not fail. EDIT: To be clear, this won't affect any actual usage of pointers in lightud since they ought to fit into that range on all popular architectures. |
|
Merged. Thanks! |
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.
LuaJIT now supports full 64-bit range light user data.