-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[master] Fix issue with even number of channels in BatchNorm #20907
[master] Fix issue with even number of channels in BatchNorm #20907
Conversation
Hey @piotrwolinski-intel , Thanks for submitting the PR
CI supported jobs: [unix-cpu, website, centos-cpu, centos-gpu, edge, unix-gpu, windows-gpu, miscellaneous, sanity, clang, windows-cpu] Note: |
@mxnet-bot run ci [centos-gpu, unix-cpu, unix-gpu] |
Jenkins CI successfully triggered : [unix-cpu, unix-gpu, centos-gpu] |
@mxnet-bot run ci [website ] |
Jenkins CI successfully triggered : [website] |
be1aaf1
to
0510abc
Compare
@mxnet-bot run ci [edge, unix-cpu, windows-gpu] |
Jenkins CI successfully triggered : [edge, unix-cpu, windows-gpu] |
@mxnet-bot run ci [windows-gpu] |
Jenkins CI successfully triggered : [windows-gpu] |
Description
Goal of this PR is to prevent bug with BatchNorm, that was seen on other versions (here for instance).
Fix is done by calling oneDNN implementations via
DNNLRun
method, not directly.