> CI tests your changes automatically so no worries there, I would prefer that > we just upgrade the oneDNN version manually (and keep the version pinned) > though instead of grabbing the latest (imagine that there is a breaking > update, the Docker image build would just stop working one day)
Thanks for your comments and suggestions. I had modified the script to pin oneDNN to the latest release v2.6, and it's easy to change the pinned version or set to build the latest release. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/pull/11140#issuecomment-1111636166 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm/pull/11140/c1111636...@github.com>
