Chip SDK multi-version dependency conflict automatic detection and isolation system

Abstract

This invention discloses an automatic detection and isolation system for multi-version dependency conflicts in chip SDKs, comprising a dependency parsing and modeling module, a conflict precision detection module, a virtual isolation compilation module, a configuration automatic generation module, and a parallel build scheduling module. The signal input of the dependency parsing and modeling module is connected to the original configuration data of multiple chip SDK versions, and the signal output of the dependency parsing and modeling module is connected to the input of the conflict precision detection module, used to parse the configuration parameters and version constraint information of the dedicated dependency libraries of each chip SDK version. The beneficial effects of this invention are: designed specifically for the unique characteristics of chip SDK compilation, hardware adaptation, and hierarchical nested dependencies, it can accurately identify chip-specific explicit and implicit dependency conflicts, solving the core defect of existing technologies that cannot adapt to chip scenarios; and it achieves fully automated closed-loop processing of dependency parsing, conflict detection, isolated deployment, configuration generation, and parallel build, fundamentally solving the problem of multi-version SDK dependency conflicts.

Description

Technical Field

[0001] This invention belongs to the field of chip software development technology, specifically relating to an automatic detection and isolation system for multi-version dependency conflicts in chip SDKs. Background Technology

[0002] With the rapid iteration and upgrading of chip technology, the same chip platform often adapts to multiple versions of SDK development toolkits. These different SDK versions have significant differences in their dependency library versions, compilation rules, and hardware adaptation parameters. During the parallel development, compilation, and adaptation of multiple SDK versions, dependency libraries from different versions are prone to incompatibility, mutual overwriting, and parameter conflicts. This can lead to chip compilation failures, program malfunctions, and hardware adaptation failures, severely impacting chip software development efficiency and product iteration progress.

[0003] Currently, there are general dependency conflict detection schemes in existing technologies, such as a method for detecting dependency conflicts in a Python environment (patent publication number CN112631607A). This scheme builds a PYPI open-source project metadata repository, establishes a global general dependency network and dependency relationship tree, detects dependency conflicts caused by version updates based on the installation dependencies of the general open-source project, and pushes a general solution. However, this existing technology has inherent limitations in scenarios and technical defects, and cannot adapt to chip SDK compilation scenarios: this scheme is designed for the general Python open-source environment, and the dependency data comes from the PYPI general open-source project, which is not adapted to... The chip SDK's unique compilation dependencies, hardware driver dependencies, and chip-level nested dependencies make it impossible to identify hidden compilation conflicts and hardware adaptation conflicts specific to the chip SDK. This solution can only detect and push general dependency conflicts, and lacks the ability to isolate and deploy conflicting components, generate dedicated compilation configurations, and build multiple versions in parallel. It cannot solve the core pain point of parallel compilation of multiple versions of the chip SDK. This solution relies on a global general dependency network to detect conflicts, and does not perform precise traversal of the chip SDK's hierarchical compilation chain. The conflict detection accuracy is low, and it is prone to missed detections and false detections, which cannot meet the high stability and high adaptability requirements of chip compilation. Summary of the Invention

[0004] The purpose of this invention is to provide an automatic detection and isolation system for multi-version dependency conflicts in chip SDKs, which solves the technical problems that existing general dependency detection technologies cannot adapt to chip SDK compilation scenarios, have low conflict detection accuracy, lack dedicated isolation compilation schemes, and cannot build multiple versions of SDKs in parallel.

[0005] To achieve the above objectives, the present invention provides the following technical solution: an automatic detection and isolation system for multi-version dependency conflicts in a chip SDK, comprising a dependency parsing and modeling module, a conflict accuracy detection module, a virtual isolation compilation module, an automatic configuration generation module, and a parallel build scheduling module; The signal input terminal of the dependency parsing and modeling module is connected to the original configuration data of multiple versions of chip SDK, and the signal output terminal of the dependency parsing and modeling module is connected to the input terminal of the conflict precision detection module. It is used to parse the configuration parameters and version constraint information of the dedicated dependency library of each version of chip SDK and construct a dedicated hierarchical dependency link model of chip SDK. The output of the conflict detection module is connected to the input of the virtual isolation compilation module. It is used to traverse the entire dependency relationship based on the hierarchical dependency link model and accurately locate the conflict points and conflict components between multiple versions of chip SDK. The output of the virtual isolation compilation module is connected to the input of the configuration automatic generation module, which is used to build a dedicated virtual isolation compilation environment for chip compilation and to partition and independently deploy and isolate the detected conflict components. The output of the automatic configuration generation module is connected to the input of the parallel construction scheduling module, and is used to automatically generate an isolated compilation configuration file that adapts to multiple versions of chip SDK based on the conflict isolation result. The parallel build scheduling module is used to load isolated compilation configuration files and schedule the non-interference parallel compilation and build of multiple versions of chip SDKs.

[0006] As a preferred technical solution of the present invention, the dependency parsing and modeling module includes an SDK configuration parsing unit, a version constraint extraction unit, and a dependency link construction unit; The SDK configuration parsing unit is used to read the compilation configuration files and dependency manifest files of each version of the chip SDK in batches, and to identify the chip SDK-specific compilation dependency rules, hardware adaptation dependency parameters and library file associations. The version constraint extraction unit is used to filter the chip adaptation version range, enforce version constraints, and compatibility version thresholds of each dependent library, remove invalid constraint parameters of general open source libraries, and retain the exclusive version constraint information necessary for chip SDK compilation. The dependency link construction unit is used to construct a chip SDK-specific dependency link model with hierarchical association attributes by associating the hierarchical dependencies of the top-level SDK, the middle-level dependency library, and the bottom-level hardware adaptation library according to the chip SDK compilation hierarchy.

[0007] As a preferred technical solution of the present invention, the hierarchical dependency link model constructed by the dependency link construction unit takes each version of the chip SDK as the top-level node and the compilation dependency library, hardware driver library and chip adaptation library associated with the SDK as the secondary nodes. Each secondary node is marked with its own version constraints, dependency priority and compilation dependency sequence, forming a hierarchical dependency tree structure in which multiple versions of SDK are independent and cross-comparable.

[0008] As a preferred technical solution of the present invention, the conflict accurate detection module includes a full-link traversal unit, a version comparison and verification unit, and a conflict point marking unit; The full-link traversal unit is used to traverse the hierarchical dependency link model corresponding to multiple versions of chip SDKs level by level, covering the full-link nodes of direct dependencies, indirect nested dependencies and implicit chip hardware dependencies. The version comparison and verification unit is used to cross-compare the version parameters of the dependency libraries with the same name and function in multiple version SDKs, and to verify whether the versions of the dependency libraries of different version SDKs exceed the mutual compatibility threshold and whether there is a forced version mutual exclusion relationship. The conflict point marking unit is used to mark library file nodes and compilation configuration nodes that have version mutual exclusion, version incompatibility, or dependency coverage conflicts as conflict points, and synchronously record the conflict type, conflict SDK version, and conflict impact range.

[0009] As a preferred technical solution of the present invention, the version comparison and verification unit distinguishes between explicit dependency conflicts and implicit dependency conflicts of the chip SDK. The explicit dependency conflicts are version mutual exclusion conflicts that are clearly marked in the configuration file, and the implicit dependency conflicts are indirect version incompatibility conflicts caused by chip hardware adaptation and compilation timing association, so as to achieve accurate identification of all types of conflicts.

[0010] As a preferred technical solution of the present invention, the virtual isolation compilation module includes an environment virtualization unit, a conflict component partitioning unit, and a resource isolation management unit; The environment virtualization unit is used to build a lightweight virtual compilation sub-environment adapted to the chip compilation scenario, allocate an independent virtual compilation space for each version of the chip SDK, and isolate the compilation resources of different versions of the SDK. The conflict component partitioning unit is used to divide the detected conflict-dependent components into independent virtual partitions, while non-conflict components adopt a shared deployment method, realizing a partitioned deployment mode that isolates conflict components and reuses non-conflict components; The resource isolation and control unit is used to manage the compilation permissions, library call paths, and hardware adaptation resources of each virtual compilation sub-environment, and to prevent conflicting components of different SDK versions from overwriting each other and interfering with parameters.

[0011] As a preferred technical solution of the present invention, the virtual compilation sub-environment built by the virtual isolation compilation module is compatible with the chip SDK-specific compilation toolchain and hardware driver adapter, abandons the general code running environment configuration, and only retains the running resources necessary for chip compilation, thereby improving the adaptability and running efficiency of isolation compilation.

[0012] As a preferred technical solution of the present invention, the automatic configuration generation module includes an isolation rule matching unit, a configuration parameter adaptation unit, and a configuration file generation unit.

[0013] Compared with the prior art, the beneficial effects of the present invention are: Designed with specific features for chip SDK compilation, hardware adaptation, and hierarchical nested dependencies, it can accurately identify chip-specific explicit and implicit dependency conflicts, solving the core defect that existing technologies cannot adapt to chip scenarios. It achieves fully automated closed-loop processing of dependency resolution, conflict detection, isolated deployment, configuration generation, and parallel building, solving the problem of multi-version SDK dependency conflicts from the root. By using a virtual partition isolation deployment mode, conflicting components are isolated and non-conflicting components are reused. While ensuring the isolation effect, compilation resources are saved, supporting the parallel construction of multiple versions of chip SDKs without interference, and significantly improving the efficiency of chip software development iteration. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the automatic detection and isolation system for multi-version dependency conflicts in the chip SDK of the present invention. Detailed Implementation

[0015] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] Please see Figure 1 This invention provides an automatic detection and isolation system for multi-version dependency conflicts in chip SDKs, including a dependency parsing and modeling module, a conflict accuracy detection module, a virtual isolation compilation module, an automatic configuration generation module, and a parallel build scheduling module; The signal input of the dependency parsing and modeling module is connected to the original configuration data of multiple versions of the chip SDK, and the signal output of the dependency parsing and modeling module is connected to the input of the conflict precision detection module. It is used to parse the configuration parameters and version constraint information of the dedicated dependency library of each version of the chip SDK and build a dedicated hierarchical dependency link model of the chip SDK. The output of the conflict precision detection module is connected to the input of the virtual isolation compilation module. It is used to traverse the entire dependency relationship based on the hierarchical dependency link model and accurately locate the version conflict points and conflicting components between multiple versions of chip SDKs. The output of the virtual isolation compilation module is connected to the input of the configuration auto-generation module to build a dedicated virtual isolation compilation environment for chip compilation, and to partition and independently deploy and isolate the detected conflicting components. The output of the automatic configuration generation module is connected to the input of the parallel build scheduling module, which is used to automatically generate an isolated compilation configuration file that adapts to multiple versions of the chip SDK based on the conflict isolation results; The parallel build scheduling module is used to load isolated compilation configuration files and schedule the non-interference parallel compilation and build of multiple versions of chip SDKs.

[0017] In this embodiment, the dependency parsing and modeling module includes an SDK configuration parsing unit, a version constraint extraction unit, and a dependency link construction unit; The SDK configuration parsing unit is used to read the compilation configuration files and dependency manifest files of various versions of the chip SDK in batches, and to identify the chip SDK-specific compilation dependency rules, hardware adaptation dependency parameters and library file associations. The version constraint extraction unit is used to filter the chip adaptation version range of each dependent library, enforce version constraints, and compatibility version thresholds, remove invalid constraint parameters of general open source libraries, and retain the exclusive version constraint information required for chip SDK compilation. The dependency link building unit is used to associate the hierarchical dependencies of the top-level SDK, mid-level dependency libraries, and bottom-level hardware adaptation libraries according to the compilation hierarchy of the chip SDK, and build a chip SDK-specific dependency link model with hierarchical association attributes. The hierarchical dependency link model built by the dependency link building unit takes each version of the chip SDK as the top-level node and the compilation dependency libraries, hardware driver libraries, and chip adaptation libraries associated with the SDK as secondary nodes. It marks the exclusive version constraints, dependency priorities, and compilation dependency timing of each secondary node, forming a hierarchical dependency tree structure that is independent and cross-comparable for multiple versions of SDK.

[0018] In this embodiment, the conflict accuracy detection module includes a full-link traversal unit, a version comparison and verification unit, and a conflict point marking unit; The full-link traversal unit is used to traverse the hierarchical dependency link model corresponding to multiple versions of chip SDKs level by level, covering the full-link nodes of direct dependencies, indirect nested dependencies and implicit chip hardware dependencies. The version comparison and verification unit is used to cross-compare the version parameters of dependency libraries with the same name and function in multiple versions of SDK, and to verify whether the versions of dependency libraries in different versions of SDK exceed the mutual compatibility threshold and whether there is a forced version mutual exclusion relationship. The conflict point marking unit is used to mark library file nodes and compilation configuration nodes that have version mutual exclusion, version incompatibility, or dependency coverage conflicts as conflict points, and synchronously record the conflict type, conflict SDK version, and conflict impact scope.

[0019] In this embodiment, the version comparison and verification unit distinguishes between explicit and implicit dependency conflicts of the chip SDK. Explicit dependency conflicts are version mutual exclusion conflicts that are clearly marked in the configuration file, while implicit dependency conflicts are indirect version incompatibility conflicts caused by chip hardware adaptation and compilation timing association, thus achieving accurate identification of all types of conflicts.

[0020] In this embodiment, the virtual isolation compilation module includes an environment virtualization unit, a conflict component partitioning unit, and a resource isolation management unit; The environment virtualization unit is used to build a lightweight virtual compilation sub-environment adapted to the chip compilation scenario, allocates an independent virtual compilation space for each version of the chip SDK, and isolates the compilation resources of different versions of the SDK. The conflict component partitioning unit is used to separate the detected conflicting dependent components into independent virtual partitions, while non-conflicting components adopt a shared deployment method, realizing a partitioned deployment mode that isolates conflicting components and reuses non-conflicting components; The resource isolation and control unit is used to manage the compilation permissions, library call paths, and hardware adaptation resources of each virtual compilation sub-environment, preventing conflicting components from different versions of the SDK from overwriting each other and interfering with parameters.

[0021] In this embodiment, the virtual compilation sub-environment built by the virtual isolation compilation module is compatible with the chip SDK-specific compilation toolchain and hardware driver adapter, abandons the general code runtime environment configuration, and only retains the runtime resources necessary for chip compilation, thereby improving the adaptability and running efficiency of isolated compilation.

[0022] In this embodiment, the automatic configuration generation module includes an isolation rule matching unit, a configuration parameter adaptation unit, and a configuration file generation unit; The isolation rule matching unit is used to match the corresponding chip SDK isolation compilation rules based on the conflict point type and the partition deployment results of the conflict components; The configuration parameter adaptation unit is used to modify the library call path, version binding parameters, and compilation priority parameters of each virtual compilation sub-environment in a targeted manner to adapt to the deployment requirements of conflicting components in isolation. The configuration file generation unit is used to automatically generate standardized, directly loadable multi-version SDK isolated compilation configuration files. The configuration files contain the independent compilation paths of each version of the SDK, conflict component isolation identifiers, and resource allocation parameters.

[0023] In this embodiment, the parallel build scheduling module includes a task allocation unit, a parallel compilation management and control unit, and a build status monitoring unit; The task allocation unit is used to allocate multi-version compilation tasks to the corresponding virtual compilation sub-environment according to the compilation requirements of each version of the SDK; The parallel compilation management unit is used to synchronously schedule multiple virtual compilation sub-environments to perform compilation and build operations simultaneously, without interfering with each other and running independently. The build status monitoring unit is used to monitor the compilation progress, conflict isolation effect, and compilation exception information of each version of the SDK in real time, and to provide real-time feedback on the parallel build status. When a compilation exception is detected, the parallel build scheduling module accurately locates the conflicting components and SDK versions corresponding to the exception, and automatically fine-tunes the isolation configuration parameters of the corresponding virtual compilation sub-environment to achieve adaptive optimization of conflict isolation and parallel build.

[0024] Although embodiments of the invention have been shown and described (see the detailed description above), it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A chip SDK multi-version dependency conflict automatic detection and isolation system, characterized in that: It includes a dependency resolution and modeling module, a conflict precision detection module, a virtual isolation compilation module, an automatic configuration generation module, and a parallel build scheduling module; The signal input terminal of the dependency parsing and modeling module is connected to the original configuration data of multiple versions of chip SDK, and the signal output terminal of the dependency parsing and modeling module is connected to the input terminal of the conflict precision detection module. It is used to parse the configuration parameters and version constraint information of the dedicated dependency library of each version of chip SDK and construct a dedicated hierarchical dependency link model of chip SDK. The output of the conflict detection module is connected to the input of the virtual isolation compilation module. It is used to traverse the entire dependency relationship based on the hierarchical dependency link model and accurately locate the conflict points and conflict components between multiple versions of chip SDK. The output of the virtual isolation compilation module is connected to the input of the configuration automatic generation module, which is used to build a dedicated virtual isolation compilation environment for chip compilation and to partition and independently deploy and isolate the detected conflict components. The output of the automatic configuration generation module is connected to the input of the parallel construction scheduling module, and is used to automatically generate an isolated compilation configuration file that adapts to multiple versions of chip SDK based on the conflict isolation result. The parallel build scheduling module is used to load isolated compilation configuration files and schedule the non-interference parallel compilation and build of multiple versions of chip SDKs.

2. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 1, characterized in that: The dependency parsing and modeling module includes an SDK configuration parsing unit, a version constraint extraction unit, and a dependency link construction unit. The SDK configuration parsing unit is used to read the compilation configuration files and dependency manifest files of each version of the chip SDK in batches, and to identify the chip SDK-specific compilation dependency rules, hardware adaptation dependency parameters and library file associations. The version constraint extraction unit is used to filter the chip adaptation version range, enforce version constraints, and compatibility version thresholds of each dependent library, remove invalid constraint parameters of general open source libraries, and retain the exclusive version constraint information necessary for chip SDK compilation. The dependency link construction unit is used to construct a chip SDK-specific dependency link model with hierarchical association attributes by associating the hierarchical dependencies of the top-level SDK, the middle-level dependency library, and the bottom-level hardware adaptation library according to the chip SDK compilation hierarchy.

3. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 2, characterized in that: The hierarchical dependency chain model constructed by the dependency chain construction unit takes each version of the chip SDK as the top-level node and the compilation dependency library, hardware driver library, and chip adaptation library associated with the SDK as the secondary nodes. Each secondary node is labeled with its own version constraints, dependency priority, and compilation dependency sequence, forming a hierarchical dependency tree structure in which multiple versions of SDK are independent and cross-comparable.

4. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 1, characterized in that: The conflict detection module includes a full-link traversal unit, a version comparison and verification unit, and a conflict point marking unit. The full-link traversal unit is used to traverse the hierarchical dependency link model corresponding to multiple versions of chip SDKs level by level, covering the full-link nodes of direct dependencies, indirect nested dependencies and implicit chip hardware dependencies. The version comparison and verification unit is used to cross-compare the version parameters of the dependency libraries with the same name and function in multiple version SDKs, and to verify whether the versions of the dependency libraries of different version SDKs exceed the mutual compatibility threshold and whether there is a forced version mutual exclusion relationship. The conflict point marking unit is used to mark library file nodes and compilation configuration nodes that have version mutual exclusion, version incompatibility, or dependency coverage conflicts as conflict points, and synchronously record the conflict type, conflict SDK version, and conflict impact range.

5. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 4, characterized in that: The version comparison and verification unit distinguishes between explicit and implicit dependency conflicts of the chip SDK. The explicit dependency conflict is a version mutual exclusion conflict explicitly marked in the configuration file, while the implicit dependency conflict is an indirect version incompatibility conflict caused by chip hardware adaptation and compilation timing association, thus achieving accurate identification of all types of conflicts.

6. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 1, characterized in that: The virtual isolation compilation module includes an environment virtualization unit, a conflict component partitioning unit, and a resource isolation and management unit. The environment virtualization unit is used to build a lightweight virtual compilation sub-environment adapted to the chip compilation scenario, allocate an independent virtual compilation space for each version of the chip SDK, and isolate the compilation resources of different versions of the SDK. The conflict component partitioning unit is used to divide the detected conflict-dependent components into independent virtual partitions, while non-conflict components adopt a shared deployment method, realizing a partitioned deployment mode that isolates conflict components and reuses non-conflict components; The resource isolation and control unit is used to manage the compilation permissions, library call paths, and hardware adaptation resources of each virtual compilation sub-environment, and to prevent conflicting components of different SDK versions from overwriting each other and interfering with parameters.

7. The chip SDK multi-version dependency conflict automatic detection and isolation system according to claim 6, characterized in that: The virtual compilation sub-environment built by the virtual isolation compilation module is compatible with the chip SDK's dedicated compilation toolchain and hardware driver adapters. It abandons the general code runtime environment configuration and only retains the runtime resources necessary for chip compilation, thereby improving the adaptability and running efficiency of isolated compilation.

8. The automatic detection and isolation system for multi-version dependency conflicts of a chip SDK according to claim 1, characterized in that: The automatic configuration generation module includes an isolation rule matching unit, a configuration parameter adaptation unit, and a configuration file generation unit.

Images