With CUDA-10.2 gone we can finally do it!
This PR mostly contains build system related changes, invasive functional ones are to be followed.
Among many expected tweaks to the build system, here are few unexpected ones:
- Force onnx_proto project to be updated to C++17 to avoid `duplicate symbols` error when compiled by gcc-7.5.0, as storage rule for `constexpr` changed in C++17, but gcc does not seem to follow it
- Do not use `std::apply` on CUDA but rely on the built-in variant, as it results in test failures when CUDA runtime picks host rather than device function when `std::apply` is invoked from CUDA code.
- `std::decay_t` -> `::std::decay_t` and `std::move`->`::std::move` as VC++ for some reason claims that `std` symbol is ambigious
- Disable use of `std::aligned_alloc` on Android, as its `libc++` does not implement it.
Some prerequisites:
- https://github.com/pytorch/pytorch/pull/89297
- https://github.com/pytorch/pytorch/pull/89605
- https://github.com/pytorch/pytorch/pull/90228
- https://github.com/pytorch/pytorch/pull/90389
- https://github.com/pytorch/pytorch/pull/90379
- https://github.com/pytorch/pytorch/pull/89570
- https://github.com/facebookincubator/gloo/pull/336
- https://github.com/facebookincubator/gloo/pull/343
-
|
||
|---|---|---|
| .. | ||
| benchmark | ||
| custom_build | ||
| fastlane | ||
| models | ||
| TestApp | ||
| TestApp.xcodeproj | ||
| TestAppTests | ||
| .clang-format | ||
| .gitignore | ||
| Gemfile | ||
| Gemfile.lock | ||
| METADATA.bzl | ||
| README.md | ||
TestApp
The TestApp is currently being used as a dummy app by Circle CI for nightly jobs. The challenge comes when testing the arm64 build as we don't have a way to code-sign our TestApp. This is where Fastlane came to rescue. Fastlane is a trendy automation tool for building and managing iOS applications. It also works seamlessly with Circle CI. We are going to leverage the import_certificate action, which can install developer certificates on CI machines. See Fastfile for more details.
For simulator build, we run unit tests as the last step of our CI workflow. Those unit tests can also be run manually via the fastlane scan command.
Run Simulator Test Locally
Follow these steps if you want to run the test locally.
-
Checkout PyTorch repo including all submodules
-
Build PyTorch for ios
USE_COREML_DELEGATE=1 IOS_PLATFORM=SIMULATOR ./scripts/build_ios.sh
- Generate on-the-fly test models
python test/mobile/model_test/gen_test_model.py ios-test
You need to install regular PyTorch on your local machine to run this script. Check https://github.com/pytorch/pytorch/tree/master/test/mobile/model_test#diagnose-failed-test to learn more.
- Create XCode project (for lite interpreter)
cd ios/TestApp/benchmark
ruby setup.rb --lite 1
- Open the generated TestApp/TestApp.xcodeproj in XCode and run simulator test.
Re-generate All Test Models
-
Make sure PyTorch (not PyTorch for iOS) is installed See https://pytorch.org/get-started/locally/
-
Re-generate models for operator test
python test/mobile/model_test/gen_test_model.py ios
python test/mobile/model_test/gen_test_model.py ios-test
- Re-generate Core ML model
cd ios/TestApp/benchmark; python coreml_backend.py
Debug Test Failures
Make sure all models are generated. See https://github.com/pytorch/pytorch/tree/master/test/mobile/model_test to learn more.
There's no debug information in simulator test (project TestAppTests). You can copy the failed test code to TestApp/TestApp/ViewController.mm and debug in the main TestApp.
Benchmark
The benchmark folder contains two scripts that help you setup the benchmark project. The setup.rb does the heavy-lifting jobs of setting up the XCode project, whereas the trace_model.py is a Python script that you can tweak to generate your model for benchmarking. Simply follow the steps below to setup the project
- In the PyTorch root directory, run
IOS_ARCH=arm64 ./scripts/build_ios.shto generate the custom build from Master branch - Navigate to the
benchmarkfolder, runpython trace_model.pyto generate your model. - In the same directory, open
config.json. Those are the input parameters you can tweak. - Again, in the same directory, run
ruby setup.rbto setup the XCode project. - Open the
TestApp.xcodeproj, you're ready to go.
The benchmark code is written in C++, you can use UI_LOG to visualize the log. See benchmark.mm for more details.