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

README inaccurately says it's chainer bindings #28

Open
ezyang opened this issue Mar 28, 2019 · 1 comment
Open

README inaccurately says it's chainer bindings #28

ezyang opened this issue Mar 28, 2019 · 1 comment

Comments

@ezyang
Copy link

ezyang commented Mar 28, 2019

If I understand recent correspondence correctly, ideep will be the official frontend for mkl-dnn, not just for chainer. README should be updated.

@gujinghui
Copy link
Contributor

@ezyang
the mkldnn-bridge for pytorch/caffe2 is being separate from ideep chainer.
we're reducing the LOC and improving the API only for pytorch/caffe2.
when done, we plan to make the mkldnn-bridge as a part of pytorch/caffe2, instead of a submodule.

zhuhaozhe pushed a commit to zhuhaozhe/ideep that referenced this issue Apr 8, 2022
zhuhaozhe pushed a commit to zhuhaozhe/ideep that referenced this issue Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants