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 766d630
Browse filesBrowse the repository at this point in the historyBrowse files
Fix the torch_cpu_library comments and make aten_bridge static
The same three-line comment sat at five link sites. It explained why the
line does not link torch, but not what torch_cpu_library does
differently, and "in a CUDA build" read as our own CUDA option rather
than how PyTorch was built.
Each site now says that torch records libtorch_cuda with a CUDA build of
PyTorch, so a CPU-only torch could not load the library, and that
torch_cpu_library does not.
At aten_bridge the old reason did not apply. aten_bridge is a static
library and is never loaded on its own. Its link matters because it is
passed on to _training_lib. But it was only static by default: with
BUILD_SHARED_LIBS=ON it became a shared library. Mark it STATIC so the
comment holds in every layout. Nothing installs it and only
_training_lib links it.
0 commit comments