Skip to content

Conversation

jsquyres
Copy link
Member

Prefix all the not-intended-to-be-public treematch symbols with
"ompi_tm_" so that they don't pollute the Open MPI library namespace.

Also, mark a bunch of symbols as "static" that are not used outside of
their respective .c files to prevent pollution of internal treematch
symbols in the Open MPI library.

Signed-off-by: Jeff Squyres [email protected]

This is related to #8262 and #8132.

Prefix all the not-intended-to-be-public treematch symbols with
"ompi_tm_" so that they don't pollute the Open MPI library namespace.

Also, mark a bunch of symbols as "static" that are not used outside of
their respective .c files to prevent pollution of internal treematch
symbols in the Open MPI library.

Signed-off-by: Jeff Squyres <[email protected]>
@jsquyres
Copy link
Member Author

Per verbal discussion with @bosilca, the treematch authors have a new version of treematch that will entail some re-coding on our side to adapt to their new API / changes.

Hence, it's "safe" to locally edit our treematch library because upstream has already diverged from us. If we don't plan to re-sync with upstream (i.e., port to their new API), we can make changes to our local treematch without consequence.

@ibm-ompi
Copy link

The IBM CI (XL) build failed! Please review the log, linked below.

Gist: https://gist.github.com/3a080052062345c652734f265cab41cb

@gpaulsen
Copy link
Member

@jsquyres Is this important for v5.0.0 ?

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.

3 participants