Debugging PCurves mac failure #4009
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
This makes the data easier to consume for interfaces that aren't integer-oriented.
For whatever reason GCC 11 through 13 will produce an incorrect result for pcurves P-521 without these volatile qualifiers. I do not know if this is caused by a bug in our asm constraints or a bug in GCC. Unfortunately as it only manifests when in amalagamtion mode it is quite difficult to reduce to a small testcase.
This reverts commit 8f8d386.
|
Conclusion: 15.3 on Aarch64 is ok Is it a bug that was fixed in 15.3? Or just a bug that only affects x86 builds? ¯\(ツ)/¯ Not entirely sure how to proceed short of just using -O2. Not interested in paying Apple $99 to get a dev account in order to report a bug they'll probably ignore. |
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.
No description provided.