-
Notifications
You must be signed in to change notification settings - Fork 43
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
[googletest] Possible False Positive of ROCMChecks WARNING #154
Comments
Dont build dependencies directly using
Due to issues with using |
@pfultz2 which way we should build
|
The warning shouldn't be ignored. And this case its even more problematic because a third-party library is changing the compilation flags for MIOpen outside of your control. Furthermore, in the future these warnings will become errors.
Its not a false positive. Following the wiki page, it suggests using a different approach than whats written in googletest. |
I also see this warning from rocThrust:
when built with FetchContent. Setting |
[Observations]
with googletest
v1.14.0
(latest version as of 10/31/2023)We observe multiple
ROCMChecks WARNING
warnings like[Likely Root Cause]:
https://github.com/google/googletest/blob/b10fad38c4026a29ea6561ab15fc4818170d1c10/googletest/cmake/internal_utils.cmake#L25
It is likely that
rocm-cmake
grep the keywords fromsuch as
CMAKE_CXX_FLAGS
andCMAKE_C_FLAGS
Should this be a false positive? How can we disable or suppress warning like this one?
The text was updated successfully, but these errors were encountered: