ArmNN allows adding new backends through the ‘Pluggable Backend’ mechanism.
Backends reside under src/backends in separate subfolders. They must have a backend.cmake file which is read automatically by src/backends/backends.cmake. The backend.cmake file under the backend specific folder is then included by the main CMakeLists.txt file at the root of the ArmNN source tree.
The backend.cmake has two main purposes:
To achieve this there are two requirements for the backend.cmake file (example taken from reference/backend.cmake)
# # Make sure the reference backend is included in the build. # By adding the subdirectory, cmake requires the presence of CMakeLists.txt # in the reference (backend) folder. # add_subdirectory(${PROJECT_SOURCE_DIR}/src/backends/reference) # # Add the static libraries built by the reference backend to the # list of libraries linked against the ArmNN shared library. # list(APPEND armnnLibraries armnnRefBackend armnnRefBackendWorkloads)
As described in the previous section, adding a new backend will require creating a CMakeLists.txt in the backend folder. This follows the standard cmake conventions, and is required to build an artifact to be linked into the ArmNN shared library. As with any cmake build, the code can be structured into subfolders and modules as the developer sees fit.
Example can be found under reference/CMakeLists.txt.
ArmNN on Android uses the native Android build system. New backends are integrated by creating a backend.mk file which has a single variable called BACKEND_SOURCES listing all cpp files to be built by the Android build system.
Example taken from reference/backend.mk:
BACKEND_SOURCES := \ RefLayerSupport.cpp \ RefWorkloadFactory.cpp \ workloads/Activation.cpp \ workloads/ArithmeticFunction.cpp \ workloads/Broadcast.cpp \ ...
For multiple backends that need common code, there is support for including them in the build similarly to the backend code. This requires adding three files under a subfolder at the same level as the backends folders. These are:
They work the same way as the backend files. The only difference between them is that common code is built first, so the backend code can depend on them.
aclCommon is an example for this concept and you can find the corresponding files: