Another INIT_DEBUG_VALUE_JPRB hack#152
Merged
Merged
Conversation
dareg
approved these changes
Jun 22, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 PR contributes yet another
INIT_DEBUG_VALUE_JPRBhack. In certain situations we can get memory corruptions because a precision dependent symbol is being linked to precision independent object libraries, which can be worked around by making it the last defined variable in the module.field_api took a very intentional design decision to keep JPRB only as an aliased symbol, that's why
INIT_DEBUG_VALUE_JPRBis unused throughout the code. It would be great if we could remove it and clean up all related workarounds.This also causes other issues with flang, as outlined in #138.