Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Make c++17 standard, update MIOpen for the new CK API#1761

Merged
JehandadKhan merged 12 commits intodevelopfrom
jd/ck_api_fix
Sep 29, 2022
Merged

Make c++17 standard, update MIOpen for the new CK API#1761
JehandadKhan merged 12 commits intodevelopfrom
jd/ck_api_fix

Conversation

@JehandadKhan
Copy link
Contributor

@JehandadKhan JehandadKhan commented Sep 16, 2022

  • Make C++17 standard for MIOpen (Required due to CK headers using C++17 features)
  • Update the MIOpen Solver to the newer CK API
  • Update the CK commit hash to include fixes required in CK
  • Will require updating the CI docker image.

template <typename T>
struct tensor_reorder_driver : tensor_reorder_base_driver
{
// NOLINTBEGIN(clang-analyzer-cplusplus.NewDeleteLeaks)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@atamazov clang-tidy insists there is a memory leak on Line 452. Could you help to take a look?

-Wno-unused-command-line-argument
-Wno-weak-vtables
-Wno-covered-switch-default
-Wno-unused-result
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we disabling this warning? This is a useful warning.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because its beyond the scope of this PR. This PR focuses on enabling CK in MIOpen. We plan to properly fix these warnings in subsequent PRs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR focuses on enabling CK in MIOpen.

Regardless of the task needed, the warnings should be required to be fixed(or suppressed locally with pragmas) for all PRs.

We plan to properly fix these warnings in subsequent PRs

If its not being fixed when driven by features/defect then it will less likely be fixed by aesthetics.

Also, CK should wait until MIOpen has C++17 fully enabled before updating their headers to use C++17.

@JehandadKhan JehandadKhan merged commit ed5d2c0 into develop Sep 29, 2022
Copy link
Contributor

@atamazov atamazov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@junliume Some Q for the context of ci_rocm530_ubuntu2004 related work.

Comment on lines +606 to +608
-modernize-use-nodiscard
-modernize-concat-nested-namespaces
-modernize-unary-static-assert
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I take care about these?

Comment on lines +633 to +643
#CPP-17 and ROCM 5.3 update related warning
-misc-confusable-identifiers
-modernize-use-nodiscard
-modernize-concat-nested-namespaces
-modernize-unary-static-assert
-modernize-macro-to-enum
-readability-simplify-boolean-expr
-readability-redundant-declaration
-hicpp-member-init
-bugprone-use-after-move
-hicpp-invalid-access-moved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and these?

-Wno-unused-command-line-argument
-Wno-weak-vtables
-Wno-covered-switch-default
-Wno-unused-result
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And this one?

@junliume
Copy link
Contributor

@junliume Some Q for the context of ci_rocm530_ubuntu2004 related work.

@atamazov yes these are related. For now we suppress the warning since they are not "new" regressions, but we want to fix them, at least suppress them at code level, to avoid global suppressions.

@junliume junliume deleted the jd/ck_api_fix branch October 10, 2022 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants