You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3a21f4d
Browse filesBrowse the repository at this point in the historyBrowse files
Shorten the torch_cpu_library comments and give aten_bridge its real reason
The same three-line comment sat at five link sites. It explained why the
line does not link torch, but not why it does not link plain torch_cpu,
and "in a CUDA build" read as our own CUDA option rather than how
PyTorch was built.
Replace it with one line at each site that names both reasons: torch
adds libtorch_cuda with a CUDA build of PyTorch, and torch_cpu adds MKL
to the link. At aten_bridge the old wording was also misleading. That
target is a static library, so it is never loaded on its own. The link
matters because a static library passes it on to _training_lib, so the
comment now says that.
0 commit comments