Support Policies#
This section describes how TensorRT versions its API, how features are deprecated and removed, how long hardware remains supported, and how to get support or report a bug.
API Versioning#
TensorRT uses a MAJOR.MINOR.PATCH version number. Its public API and ABI compatibility policy generally follows Semantic Versioning 2.0.0, subject to exceptions called out in the release notes. For example, the safety and consistency-checker API signature changes documented for TensorRT 11.3.0 require matching headers and libraries. Do not infer compatibility for those surfaces from the version number alone. Version numbers otherwise change as follows:
MAJOR version when making incompatible API or ABI changes.
MINOR version when adding functionality in a backward-compatible manner.
PATCH version when making backward-compatible bug fixes.
Warning
Semantic versioning does not extend to serialized objects by default. To reuse plan files and timing caches, a version compatible engine must be used, otherwise version numbers must match across major, minor, patch, and build versions. Some exceptions exist for the safety runtime as detailed in the NVIDIA DriveOS Developer Guide.
TensorRT 11.x does not produce calibration caches. The IInt8Calibrator interface that wrote them was removed in TensorRT 11.0.0 along with implicit quantization, so there is no calibration-cache compatibility to state. Quantization parameters now travel in the model graph as quantize and dequantize layers. Refer to NVIDIA TensorRT Migration Guide.
Deprecation Policy#
Deprecation informs developers that some APIs and tools are no longer recommended. TensorRT has the following deprecation policy, beginning with version 8.0:
Deprecation notices are communicated in the Release Notes.
When using C++ API:
API functions are marked with the
TRT_DEPRECATED_APImacro.Enums are marked with the
TRT_DEPRECATED_ENUMmacro.All other locations are marked with the
TRT_DEPRECATEDmacro.Classes, functions, and objects will have a statement documenting when they were deprecated.
When using the Python API, deprecated methods and classes will issue deprecation warnings at runtime if they are used.
TensorRT provides a 12-month migration period after the deprecation.
APIs and tools continue to work during the migration period.
After the migration period ends, APIs and tools are removed in a manner consistent with semantic versioning.
For any APIs and tools specifically deprecated in TensorRT 7.x, the 12-month migration period starts from the TensorRT 8.0 GA release date.
Hardware Support Lifetime#
TensorRT 8.5.3 was the last release supporting NVIDIA Kepler (SM 3.x) and NVIDIA Maxwell (SM 5.x) devices. These devices are no longer supported in TensorRT 8.6. NVIDIA Pascal (SM 6.x) devices were deprecated in TensorRT 8.6. TensorRT 10.4 was the last release supporting NVIDIA Volta (SM 7.0) devices. TensorRT 11.5.0 requires compute capability 7.5 or later. Refer to the Support Matrix section for more information.
Support#
Support, resources, and information about TensorRT can be found online at https://developer.nvidia.com/tensorrt. This includes blogs, samples, and more.
You can also access the NVIDIA Developer TensorRT forum at https://forums.developer.nvidia.com/c/ai-data-science/deep-learning/tensorrt/ for all things related to TensorRT. This forum offers the possibility of finding answers, making connections, and getting involved in discussions with customers, developers, and TensorRT engineers.
Reporting Bugs#
NVIDIA appreciates all types of feedback. If you encounter any problems, follow the instructions in the Reporting TensorRT Issues section to report the issues.