Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix compile errors in the Verbs API #278

Merged
merged 3 commits into from
May 9, 2024
Merged

Fix compile errors in the Verbs API #278

merged 3 commits into from
May 9, 2024

Conversation

etremel
Copy link
Contributor

@etremel etremel commented May 9, 2024

Since we haven't used the Verbs version of SST and RDMC in a while, there were a bunch of compile errors if you actually used the -DUSE_VERBS_API flag. I fixed them so that Derecho can at least compile when you use this flag. This does not mean the Verbs API has been tested, though, and it definitely won't work with the new OOB memory buffer commands.

Apparently we haven't tested the -DUSE_VERBS_API flag in a while,
because there are a bunch of compile errors if you use it. Some are due
to minor changes to Derecho's internals that were never propagated to
verbs.hpp/cpp, like the ip_addr_t declaration moving inside the derecho
namespace. The rest are due to the new OOB API only being implemented
on LibFabrics. I added declarations for the OOB functions to the Verbs
interface, with function bodies that simply throw exceptions, so that
Derecho can at least compile with the Verbs interface (even if none of
the OOB functions actually work).
While debugging the compile errors caused by enabling USE_VERBS_API, I
noticed that connection_manager.hpp was improperly putting node_id_t
into the global namespace even though we intended it to be scoped within
derecho. This was inadvertently hiding a bunch of improper uses of
node_id_t that should have been caught back when we first put node_id_t
inside the derecho namespace.
My earlier commit that fixed USE_VERBS_API compile issues used the
quotes style for including headers with full paths, but now we've
changed to using the brackets style.
@etremel etremel merged commit 4fb7f95 into master May 9, 2024
1 check passed
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.

None yet

1 participant