[1.x][submodule] Upgrade oneDNN to v2.0

[bartekkuncer]

This change upgrades oneDNN on branch 1.x to v2.0.

[mxnet-bot]

Hey @bartekkuncer , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [centos-cpu, miscellaneous, windows-cpu, website, centos-gpu, sanity, clang, edge, unix-cpu, windows-gpu, unix-gpu]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[bartekkuncer]

@szha Please help with the merge. This change just upgrades oneDNN used by mxnet to v2.0 on branch 1.x.

[bartekkuncer]

@mxnet-bot run ci [unix-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-gpu]

[szha]

I think this will impact those who integrate with pip through the included header files.

[bartekkuncer]

I think this will impact those who integrate with pip through the included header files.

@szha Is there a way I can help with that?

[bartekkuncer]

@mxnet-bot run ci [unix-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-gpu]

[bartekkuncer]

@szha Hi, can this change be merged now?

[bartekkuncer]

@szha Hi, can we upgrade oneDNN to v2.0 on 1.x? :)

[szha]

@bartekkuncer I think we can, provided that downstream users/developers don't have to make code changes to integrate with mxnet. This means everything should be consistent, including function signatures (and integrating with a compatibility layer is ok), header files and locations, dynamically loaded dependencies.

[bartekkuncer]

@bartekkuncer I think we can, provided that downstream users/developers don't have to make code changes to integrate with mxnet. This means everything should be consistent, including function signatures (and integrating with a compatibility layer is ok), header files and locations, dynamically loaded dependencies.

@szha I believe the change keeps the file location consistency with previous state of the branch.

[access2rohit]

I cannot see UNIX CPU and GPU for this PR. I get the following error:

URI: | /job/mxnet-validation/job/unix-cpu/job/PR-19670/4/display/redirect
-- | --
404
Not Found
Stapler

[szha]

https://jenkins.mxnet-ci.amazon-ml.com/job/mxnet-validation/job/unix-cpu/job/PR-19670/4/display/redirect
https://jenkins.mxnet-ci.amazon-ml.com/job/mxnet-validation/job/unix-gpu/job/PR-19670/6/display/redirect