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

Compiler warnings from intel and nvcc #1999

Closed
PhilMiller opened this issue Oct 18, 2022 · 3 comments · Fixed by #2000
Closed

Compiler warnings from intel and nvcc #1999

PhilMiller opened this issue Oct 18, 2022 · 3 comments · Fixed by #2000
Assignees

Comments

@PhilMiller
Copy link
Member

Describe the bug

Commit 8315da, as built on the SNL machines

Intel:

/.../vt/tests/unit/lb/test_lb_data_comm.cc(135): warning #177: function "vt::tests::unit::comm::<unnamed>::ReduceMsg::serialize(SerializerT &) [with SerializerT=checkpoint::Serializer]" was declared but never referenced

    void serialize(SerializerT& s) {
         ^

nvcc the above, and additionally:

/.../vt/tests/unit/collection/test_collection_group.extended.cc(57): warning: variable "vt::tests::unit::handler_executed" was set but never used
@PhilMiller PhilMiller self-assigned this Oct 18, 2022
@PhilMiller
Copy link
Member Author

For Intel, the code is doing this, which should silence the warning:

#if defined(__INTEL_COMPILER)
#pragma warning(push)
#pragma warning(disable : 177)
#endif

@PhilMiller
Copy link
Member Author

None of the (quasi-)documented approaches to quieting nvcc locally seem to work. So, I'm trying a workaround of just sticking (void)&ReduceMsg::serialize<checkpoint::Serializer>; in one of the test functions, to add a reference

@PhilMiller
Copy link
Member Author

Follow-on to #1955 whose fix didn't seem to work

PhilMiller added a commit that referenced this issue Oct 18, 2022
PhilMiller added a commit that referenced this issue Oct 18, 2022
PhilMiller added a commit that referenced this issue Oct 18, 2022
cz4rs pushed a commit that referenced this issue Nov 8, 2022
cz4rs pushed a commit that referenced this issue Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant