Document transfer methods, quality inspection methods, and related devices
By acquiring and organizing exemption guidance information, generating transferable exemption file information, and automating the transfer of exemption files, the usability and efficiency issues in RTL quality inspection are resolved, and the standardized transfer and efficient use of exemption files are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-24
- Publication Date
- 2026-03-13
AI Technical Summary
In traditional RTL quality checks, the inheritance of exemption documents is not streamlined enough and has poor usability, resulting in low document processing efficiency. Furthermore, the same exemption document may be used repeatedly in different stages, introducing unnecessary problems.
A file transfer method is provided, which obtains exemption guidance information, organizes and expands it after deduplication to generate transferable exemption file information, and automatically executes the exemption file transfer process to ensure that the file is compatible with the current level of invocation.
It improves the ease of use and correctness of file retrieval for RTL quality checks, reduces the workload of repetitive manual checks, and enhances the inheritability of exemption files and the efficiency of checks.
Smart Images

Figure CN121168361B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of chip technology, and in particular to a file transfer method, a quality inspection method, and related apparatus. Background Technology
[0002] Register Transfer Level (RTL) quality checks are an essential part of digital chip design. They are used to avoid problems such as non-standard code, synthesizability defects, and synchronous / asynchronous path errors. They aim to enhance the integrability and synthesizability of the design and protect its functionality. Completing RTL quality checks during the design process can improve the reliability of the chip.
[0003] like Figure 1 As shown, in large-chip scenarios, a layered approach is typically used to perform RTL quality checks, from block to subsystem to chip, to mitigate the massive number of warnings at the chip level. Each layer generates a corresponding waiver file, which is then promoted / migrated to the next higher layer, ultimately producing a chip-level RTL quality check report, or simply a check report. It's important to note that the waiver file transfer process can include, but is not limited to, promotion / migrating. This transfer process allows the waiver file of the current layer to be adapted for use by the layer above, thus enabling the transfer of waiver files to higher layers for their use. Figure 1 Modules 1 to n can be represented by block_0, block_1, ..., block_n, and subsystems 1 to m can be represented by subsys_0, subsys_1, ..., subsys_m, where n and m are positive integers.
[0004] The generation and use of RTL quality check waivers currently largely rely on the instruction-triggered process of inspection tools (such as SpyGlass) to generate the original waiver files (original waiver files) for each inspection level. Figure 2 As shown, taking the waiver promotion in a large SoC (System on Chip) scenario as an example, the inspection tool also supports command-triggered modification of the original waiver file for sub-parts (e.g., Figure 2The sub-design waiver file (i.e., the sub-design waiver file) is converted into an upgraded waiver file (the promoted waiver file) and then input into the higher-level RTL quality checkflow. It should be noted that... Figure 2 The sub-parts in a hierarchy are relative to their higher-level counterparts. For example, a block level is a sub-part of a subsystem level, and a subsystem level is a sub-part of a chip level. Furthermore, Figure 2 The term "sub-part RTL file" refers to the RTL-related files of the sub-part. "RTL quality check" refers to the RTL quality check at this level. "Sub-part design check report" refers to the check report of the level to which the sub-part belongs. "Upper-level RTL file" refers to the RTL-related files of the upper level. "Upper-level design check report" refers to the check report of the upper level.
[0005] However, in traditional technologies, the inheritance of exemption files between sub-sections and upper-level RTL quality checks is not streamlined enough. File processing between two quality checks may introduce unnecessary problems due to manual errors by engineers. Furthermore, traditional technologies lack clear management of exemption files, directly using input files for waiver promotion. In large-scale SoC scenarios, some lower-level exemption files may be reused repeatedly, requiring improved file reusability. Moreover, the same exemption file may be repeatedly used in the same local environment at different stages of chip design, leading to inefficiency due to repeated analysis / generation of the same local file in traditional technologies. Further, there is no clearly defined and standardized waiver promotion flow from block to subsystem to top level, resulting in poor usability.
[0006] In conclusion, traditional RTL quality inspection is not very user-friendly, which affects the effectiveness of quality inspection. Summary of the Invention
[0007] Therefore, it is necessary to provide a document transfer method, a quality inspection method, and related apparatus that can improve the quality inspection effect in response to the above-mentioned technical problems.
[0008] In a first aspect, this application provides a document transfer method, the method comprising: obtaining exemption guidance information; the exemption guidance information being used to indicate the exemption file corresponding to the sub-part of the current level; organizing the exemption guidance information to obtain transferable exemption file information; and, based on the transferable exemption file information, transferring the exemption file corresponding to the sub-part to the current level.
[0009] In one embodiment, the exemption guidance information is organized to obtain transferable exemption document information, including: confirming the authenticity of the exemption guidance information; if it is authentic, the exemption guidance information is expanded and deduplicated to obtain transferable exemption document information.
[0010] In one embodiment, the exemption guidance information includes the hierarchical identifier of the sub-part and the file path of the exemption file corresponding to the sub-part; the transferable exemption file information includes the hierarchical identifier and file path of the exemption file to be transferred; expanding and deduplicating the exemption guidance information to obtain the transferable exemption file information includes: searching for the corresponding subset directory of exemption guidance in the public library according to the hierarchical identifier of the sub-part until the subset directory index is completed; deduplicating the hierarchical identifier of the sub-part and the file path of the exemption file corresponding to the sub-part, as well as the hierarchical identifier and the file path of the exemption file under the subset directory, to obtain the hierarchical identifier and file path of the exemption file to be transferred.
[0011] In one embodiment, the exemption guidance information takes the form of at least one information format, such as a document or a list; the transferable exemption document information takes the form of at least one information format, such as a document or a list.
[0012] In one embodiment, based on the transferable exemption file information, the exemption file corresponding to the sub-part is passed to the current level, including: comparing the versions of the exemption file to be passed based on the transferable exemption file information, and determining the transmission method of the exemption file to be passed according to the version comparison result; wherein, the transmission method includes the version of the exemption file to be passed, and whether to perform transmission processing for the exemption file to be passed; the transmission processing is used to adapt the exemption file to be passed to the call of the current level.
[0013] In one embodiment, the version comparison of the exemption file to be transferred is performed based on the transferable exemption file information. Based on the version comparison result, the transfer method of the exemption file to be transferred is determined, including: obtaining the public library file version of the exemption file to be transferred in the public library and the local file version of the exemption file to be transferred locally based on the transferable exemption file information; when the local file version is inconsistent with the public library file version, a transfer instruction for performing transfer processing on the exemption file to be transferred in the public library file version is generated, and an import instruction for importing the transferred exemption file to be transferred into the current level is generated; when the local file version is consistent with the public library file version, an import instruction for importing the exemption file to be transferred in the local file version into the current level is generated.
[0014] In one embodiment, the transferable exemption file information includes auxiliary information of the exemption file to be transferred; based on the transferable exemption file information, the exemption file corresponding to the sub-part is transferred to the current level, including: when the auxiliary information indicates that the exemption file to be transferred is a whitelisted file, the transfer method of the exemption file to be transferred is confirmed according to the exemption guidance information; wherein, the transfer method includes whether to perform transfer processing on the exemption file to be transferred; the transfer processing is used to adapt the exemption file to be transferred to the call of the current level.
[0015] In one embodiment, the method of transmitting the exemption file to be transmitted is determined according to the exemption guidance information, including: generating at least one of a transmission instruction and an import instruction according to the exemption guidance information; wherein the transmission instruction is used to instruct the exemption file to be transmitted to perform transmission processing, and the import instruction is used to instruct the exemption file to be transmitted or the exemption file to be transmitted after transmission processing to be imported into the current level.
[0016] Secondly, this application also provides a quality inspection method, which includes: obtaining RTL code-related files and exemption files corresponding to the sub-parts of the current level; wherein the exemption files corresponding to the sub-parts are obtained by the file transfer method described above; and performing RTL quality inspection based on the RTL code-related files and the exemption files corresponding to the sub-parts to obtain the RTL quality inspection result of the current level.
[0017] In one embodiment, the method further includes uploading one or more of the following to a public library: RTL code-related files, RTL quality check results for the current level, exemption files for the current level, and exemption guidance information.
[0018] In one embodiment, the method further includes storing one or more of the following locally: transferable exemption file information, transfer-processed exemption file to be transferred, and transfer instructions.
[0019] Thirdly, this application also provides a document transfer device, the device comprising:
[0020] The guidance information acquisition module is used to acquire exemption guidance information; the exemption guidance information is used to indicate the exemption file corresponding to the sub-part of the current level;
[0021] The information processing module is used to process the exemption guidance information to obtain transferable exemption document information;
[0022] The file transfer module is used to transfer the exemption file corresponding to the sub-part to the current level based on the transferable exemption file information.
[0023] Fourthly, this application also provides a quality inspection device, the device comprising:
[0024] The file acquisition module is used to acquire RTL code-related files and exemption files corresponding to the sub-parts of the current level; wherein, the exemption files corresponding to the sub-parts are obtained using the file transfer method described above;
[0025] The quality inspection module is used to perform RTL quality checks based on RTL code-related files and exemption files corresponding to sub-parts, and obtain the RTL quality inspection results for the current level.
[0026] Fifthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.
[0027] Sixthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.
[0028] In a seventh aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described method.
[0029] The aforementioned document transfer method, quality inspection method, and related apparatus acquire exemption guidance information, organize the exemption guidance information to obtain transferable exemption file information, and then, based on the transferable exemption file information, transfer the exemption file corresponding to the sub-part to the current level. The exemption guidance information is used to indicate the exemption file corresponding to the sub-part at the current level. This application embodiment supports transferring the exemption file of the sub-part to the current level for use, automating the transfer of exemption files in RTL quality inspection, providing a basic environment for the ease of use of exemption files and the correctness of file calls, reducing the workload of manually repeating checks on exemptable items, and conforming to the usage scenario of large-chip RTL quality inspection. Attached Figure Description
[0030] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0031] Figure 1 This is a diagram illustrating the quality inspection hierarchy.
[0032] Figure 2 This is a diagram illustrating the transfer of exemption documents.
[0033] Figure 3 This is a flowchart illustrating a file transfer method in one embodiment.
[0034] Figure 4 This is a schematic diagram of the expansion and deduplication process in one embodiment.
[0035] Figure 5 This is a flowchart illustrating the process of a subset directory index in one embodiment.
[0036] Figure 6 This is a schematic diagram of the deduplication process in one embodiment.
[0037] Figure 7 This is a schematic diagram of the instruction generation process in one embodiment.
[0038] Figure 8 This is a flowchart illustrating a quality inspection method in one embodiment.
[0039] Figure 9 This is a schematic diagram of the specific process of quality inspection in one embodiment.
[0040] Figure 10 This is a structural block diagram of a file transfer device in one embodiment.
[0041] Figure 11 This is a structural block diagram of a quality inspection device in one embodiment.
[0042] Figure 12 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0043] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0044] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the solutions, or any combination of multiple solutions. In addition, the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0045] Based on the aforementioned traditional technologies, this application embodiment automates the execution of the above-mentioned use cases through a complete workflow, improving usability. Taking the promotion process used for exemption documents as an example, this application embodiment proposes an RTL quality check waiver promotion flow. This flow automates the execution of RTL quality check waiver promotion and its usage. The flow may include the identification and extraction of the original exemption documents, the automated execution of exemption promotion based on the original exemption document directory index, and the invocation of tools to perform RTL quality checks and generate a target-level RTL quality check report. Furthermore, based on the RTL quality check waiver promotion flow, a management method for RTL quality check exemption documents that can be agreed upon with engineers is proposed, providing a foundational environment for ease of use and correct document retrieval.
[0046] It is understood that the exemption document in the embodiments of this application is used to indicate that the corresponding error is exempt (i.e., an error that does not need to be resolved immediately or is tolerable), such as a human exemption; the sub-parts in the embodiments of this application are relative to their upper layers, for example, the block level is a sub-part of the subsystem level, and the subsystem level is a sub-part of the chip level. It should be noted that the beneficial effects or technical problems solved by the embodiments of this application are not limited to this one, and may also be other implicit or related problems, which can be referred to in the following description of the embodiments.
[0047] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0048] In one exemplary embodiment, such as Figure 3 As shown, a file transfer method is provided. Taking the application of this method to RTL quality inspection as an example, it can be understood that this method can also be applied to exemption file transfer functions, such as the waiver promotion function, and can also be applied to related processes that enable or include the waiver promotion function, such as the waiver promotion process, and can be implemented in conjunction with the RTL quality inspection exemption file management method. The method may include the following steps S102 to S106.
[0049] Step S102: Obtain exemption guidance information; the exemption guidance information is used to indicate the exemption file corresponding to the sub-part of the current level.
[0050] Based on exemption guidance information (which can be simply referred to as exemption guidance, such as waiver promotion guidance), the flow can extract necessary information from exemption-related documents (waiver-related documents). For example, exemption guidance information can be used to indicate the exemption document corresponding to the sub-section of the current level. Optionally, the flow can read waiver promotion guidance.
[0051] Taking the implementation of the exemption enhancement function to perform RTL quality checks at the current level as an example, based on RTL quality check exemption file management, engineers can prepare exemption-related files, such as RTL-related files, exemption files for sub-parts (e.g., block-level), and lists and paths of referenced sub-part exemption files. For example, an RTL / waiver file can be entered, and flow options can be configured. It can be understood that by preparing exemption-related files, the flow clearly defines the scope of exemption files that need to be included in this RTL quality check, preventing redundant or insufficient identification that could reduce the quality of the RTL quality check.
[0052] Specifically, regarding the exemption guidance information in the embodiments of this application, the exemption guidance information may take the form of a file, a list, or other information formats. For example, the exemption guidance information may take at least one of the forms of a file or a list. In some embodiments, the exemption guidance information may include a hierarchy identifier of a sub-part and the file path of the exemption file corresponding to the sub-part. The hierarchy identifier may be used to indicate the hierarchy to which the sub-part belongs.
[0053] Optionally, taking the exemption guidance information using an exemption guidance file (e.g., a waiver promotion guidance file) as an example, the exemption guidance file can be a list file. The list content should at least include the sub-part hierarchy identifier passed by the execution file (e.g., the sub-part top module, i.e., the sub-part module information, which can be represented by module_A, module_B, etc.), and the file path of the exemption file corresponding to that sub-part (e.g., the path on the local machine or in a public library, which can be represented by waiver path_A, waiver path_B, etc.), for subsequent content extraction in the flow. Considering the convenience of engineers using the flow, the exemption-related files provided by engineers do not need to be restricted to one form, but they need to provide the above necessary information. The specific format can be agreed upon by the engineers so that the necessary information can be extracted according to the rules when the flow is built.
[0054] Step S104: Organize the exemption guidance information to obtain transferable exemption document information.
[0055] Specifically, once exemption guidance information is obtained, the process can organize the exemption guidance information to obtain information on transferable exemption documents. That is, this application supports the screening of exemption documents and realizes the automated organization of the list of exemption documents for sub-parts.
[0056] Among them, the transferable exemption document information can refer to the relevant information of the exemption documents that can be transferred to the current level sub-part after being sorted and confirmed, thereby reducing the workload of manually repeating the inspection of exemptable items; optionally, the transferable exemption document information can take at least one of the information forms of documents or lists, and this application does not limit it in this regard.
[0057] For example, taking exemption guidance information using an exemption guidance file as an example, the process collects the exemption guidance file for the sub-sections provided by the engineer and automatically performs sub-section exemption file organization. Optionally, taking transferable exemption file information using a list of exemption files to be transferred (e.g., a list of waiver files to be promoted) as an example, before organizing the information, the process can recreate a list of waiver files to be promoted in a local path to write the sub-section module information that needs to be transferred later (e.g., exemption upgrade). In some embodiments, the written content includes at least the top module of the waiverpromotion sub-section, and the path of the exemption file corresponding to that sub-section in the local or public library. In addition, the process can selectively write other auxiliary information according to the optional transfer instructions (e.g., waiverpromotion instructions) of the RTL quality inspection tool (a tool used to perform quality inspection methods).
[0058] It should be noted that the above options can be used to indicate whether file transfer is supported or not. Auxiliary information can include a whitelist, thereby enabling the scalability and flexibility of file transfer and improving ease of use.
[0059] Step S106: Based on the transferable exemption file information, pass the exemption file corresponding to the sub-part to the current level.
[0060] Specifically, once transitive exemption file information is obtained, the process can pass the exemption file corresponding to the sub-part to the current level based on the transitive exemption file information, so that the inheritance of exemption files between the sub-part and the upper-level RTL quality inspection can be proceduralized.
[0061] The above file transfer method clarifies the file transfer process at each level. For example, it clarifies the standardized file transfer process from module (block) to subsystem (subsys) and then to top (such as chip). This process is automatically executed to be compatible with the above use cases and improves ease of use.
[0062] Regarding the organization of exemption guidance information, in one embodiment, the exemption guidance information is organized to obtain transferable exemption document information, including: confirming the authenticity of the exemption guidance information; if it is authentic, the exemption guidance information is expanded and deduplicated to obtain transferable exemption document information.
[0063] Specifically, the process can extract the exemption file information for each sub-section described in the exemption guidance information and verify its authenticity. If a mismatch occurs, such as an empty exemption file path, the process can provide an error message. For example, if the transferable exemption file information uses a list of exemption files to be transferred (e.g., a list of promotion waivers), before organizing the information, the process can recreate a list of promotion waivers in a local path, and then verify the exemption file information for each sub-section before writing it into the promotion waiver list.
[0064] For authentic exemption guidance information, the process can expand and deduplicate this information to obtain transferable exemption file information. Expansion can refer to expanding the exemption guidance information based on exemption guidance content in a public library (such as exemption guidance files and related paths), thereby enabling a complete search for potentially referenced exemption files. Furthermore, deduplication reduces redundant instructions and filters directly and indirectly indexed content, handling potential abnormal use cases.
[0065] In some embodiments, the exemption guidance information includes the hierarchy identifier of the sub-part and the file path of the exemption file corresponding to the sub-part; the transferable exemption file information includes the hierarchy identifier and file path of the exemption file to be transferred; such as Figure 4 As shown, the exemption guidance information is expanded and deduplicated to obtain transferable exemption document information, including steps S202 to S204.
[0066] Step S202: Based on the hierarchical identifier of the sub-part, search for the corresponding subset directory of exemption guidelines in the public library until the subset directory index is complete.
[0067] Specifically, the exemption guidance information may include the hierarchical identifier of the sub-section and the file path of the exemption file corresponding to the sub-section; further, the transferable exemption file information may include the hierarchical identifier and file path of the exemption file to be transferred. Here, the exemption file to be transferred may refer to the sub-section exemption file that has been organized and determined to be transferable to the current level.
[0068] The subset directory of the exemption guidelines can refer to the public library exemption (waiver) subset directory. In this embodiment of the application, the flow supports indexing of the subset directory to reduce the workload of manually indexing all underlying exemption files.
[0069] Regarding the waiver subset directory index, taking the following as an example: waiver guidance information uses waiver guidance files (e.g., waiver promotion guidance); the flow is a waiver promotion flow; transferable waiver file information uses a list of waiver files to be transferred (e.g., a list of waivers to be promoted); and the hierarchy identifier uses the top module. Figure 5 As shown, the process can read the input waiver promotion guidelines. Based on the RTL quality check exemption file management method, it searches the public library path for all top modules in the file to see if a subset waiver promotion guide list exists. If it exists, it opens the file, queries the path location of the top modules and exemption files in the subset directory in the public library, and automatically indexes new waiver promotion information and writes it into the list of waivers to be promoted. The process gradually indexes until no new subset directories exist.
[0070] Understandable. Figure 5 The modules_A,_B, and_C shown represent the hierarchical identifiers of sub-parts (e.g., the top module of a sub-part, i.e., the sub-part module information). Waiter paths_A,_B, and_C represent the file paths of the waiver files corresponding to the sub-parts. Specifically, waiver path_A is the file path of the waiver file corresponding to the sub-part with the hierarchical identifier module_A, waiver path_B is the file path of the waiver file corresponding to the sub-part with the hierarchical identifier module_B, and waiver path_C is the file path of the waiver file corresponding to the sub-part with the hierarchical identifier module_C.
[0071] also, Figure 5The public library waiver subset directory shown includes waiter_A, waiter_B, and waiter_C, which can refer to the waiver guidance content in the public library (i.e., the subset waiver promotion guidance list), namely, waiver guidance file waiter_A, waiver guidance file waiter_B, and waiver guidance file waiter_C. Further, waiter_A0 and waiter_A1 can be the guidance information corresponding to the waiver guidance file waiter_A (i.e., new waiver promotion information). Optionally, the guidance information waiter_A0 can include a level identifier (module_A0) and a file path (waiver path_A0), and the guidance information waiter_A1 can include a level identifier (module_A1) and a file path (waiver path_A1).
[0072] It should be noted that regarding the management of RTL quality check exemption files during the cleanup phase, the workflow can read the content of exemption guidance information (such as waiver promotion guidance) and then perform indexing of subset directories as configured. The purpose of subset directory indexing is to completely search for exemption files that may be referenced by sub-sections. Therefore, sub-sections need to complete the check and upload it to the current level for use. The subset directory index of the current level will only index files on the public library. The list of waivers to be promoted generated in this phase is only used in this RTL quality check, is generated only in the local path, and does not need to be uploaded to the public library.
[0073] By expanding upon this, the application provides a configurable subset of the waiver directory index based on the file version maintenance of the public library. This enhances the inheritability of public library exemption files from the level where the sub-part is located to the current level (e.g., from the block level to the top level). The process can directly or indirectly reference exemption files on public libraries that have been verified by RTL quality checks, simplifying the file preparation process and improving the efficiency of the checks.
[0074] Step S204: Deduplicate the hierarchical identifier of the sub-part, the file path of the exemption file corresponding to the sub-part, and the hierarchical identifier and file path of the exemption file under the subset directory to obtain the hierarchical identifier and file path of the exemption file to be transmitted.
[0075] Specifically, the process can deduplicate the hierarchical identifiers of the sub-parts and the file paths of the corresponding exemption files, as well as the hierarchical identifiers and file paths of the exemption files under the subset directory, thereby determining the exemption files to be transmitted. Among these, the hierarchical identifiers and file paths of the exemption files to be transmitted can be obtained.
[0076] This application embodiment, through deduplication, ensures that the same level identifier and file path repeatedly pointed to during the indexing process will only be indexed once, thereby reducing redundant instructions generated. At the same time, it can also filter the content of direct and indirect indexing and handle possible abnormal use cases.
[0077] like Figure 6 As shown, regarding the indexing and deduplication of the waiver subset directory, taking the waiver guidance information using waiver guidance files (e.g., waiver promotion guidance), the flow being a waiver promotion flow, the transferable waiver file information using a list of waiver files to be transferred (e.g., a list of waivers to be promoted), and the hierarchy identifier using the top module as an example, deduplication is used when repeatedly pointing to the same set of top modules and waiver file paths during direct indexing and indirect indexing of the subset directory; these will only be indexed once. The flow will record newly appearing top module and waiver file paths; duplicate information will be ignored. If duplicate information contains inconsistent parameters, the flow will provide an error message.
[0078] It should be noted that, Figure 6 The module_A and module_B shown represent the hierarchical identifiers of the sub-parts (e.g., the top module of the sub-parts, i.e., the sub-part module information). Waiter path_A and waiver path_B represent the file paths of the waiver files corresponding to the sub-parts. Waiter path_A is the file path of the waiver file corresponding to the sub-part with the hierarchical identifier module_A, and waiver path_B is the file path of the waiver file corresponding to the sub-part with the hierarchical identifier module_B.
[0079] also, Figure 6The public library waiver subset directory shown includes waiter_A and waiter_B, which can refer to waiver guidance content (e.g., waiver guidance files) in the public library. waiter_AA and waiter_AB are the guidance information corresponding to the waiver guidance file waiter_A. The guidance information waiter_AA includes a hierarchy identifier (module_AA) and a file path (waiver path_AA, i.e., waiter path_AA), and the guidance information waiter_AB includes a hierarchy identifier (module_AB) and a file path (waiver path_AB, i.e., waiter path_AB). Similarly, waiter_BB and waiter_AB can be the guidance information corresponding to the waiver guidance file waiter_B. The guidance information waiter_BB includes a hierarchy identifier (module_BB) and a file path (waiver path_BB, i.e., waiter path_BB), and the guidance information waiter_AB includes a hierarchy identifier (module_AB) and a file path (waiver path_AB, i.e., waiter path_AB). Based on the embodiments of this application, module_AB and waiter path_AB can be deduplicated.
[0080] Furthermore, the process reads the sub-section waiver promotion guidance file, as well as performs sub-section directory indexing and deduplication, and flattens out all indexed sub-section waiver information to generate a list of waivers to be promoted.
[0081] The above file transfer method supports indexing of subset directories and deduplication of exemption files with the same level identifier (e.g., top module), which can reduce the workload of engineers manually indexing all underlying exemption files.
[0082] In one embodiment, step S106 may include: comparing the versions of the exemption file to be transferred based on the transferable exemption file information, and determining the transfer method of the exemption file to be transferred according to the result of the version comparison; wherein, the transfer method includes the version of the exemption file to be transferred, and whether to perform transfer processing for the exemption file to be transferred; the transfer processing is used to adapt the exemption file to be transferred to the current level of invocation.
[0083] Specifically, this application embodiment improves the reliability of file usage and enhances the inheritability of local files through version comparison, thereby increasing inspection efficiency. The process can compare the versions of the exemption files to be transferred based on the transferable exemption file information, and determine the transfer method of the exemption files based on the version comparison results.
[0084] In this embodiment, the transfer method may include the version of the exemption file to be transferred, and whether to perform transfer processing on the exemption file to be transferred; the transfer processing is used to adapt the exemption file to be transferred to the current level of invocation. That is, this application can determine the exemption files to be transferred that need to be transferred and the exemption files to be transferred that do not need to be transferred, so that the flow can support omitting the transfer processing action. For exemption files to be transferred that do not need to be transferred, they can be directly invoked. Thus, when performing RTL quality checks multiple times on the same level in the same folder, the inheritability of local files is enhanced and the inspection efficiency is improved.
[0085] It is understood that the transfer process in the embodiments of this application may include, but is not limited to, promotion / migration. The version of the exemption file to be transferred may include, but is not limited to, public library file version and local file version.
[0086] Regarding the determination of the transfer method, in some embodiments, the version comparison of the exemption file to be transferred is performed based on the transferable exemption file information. According to the result of the version comparison, the transfer method of the exemption file to be transferred is determined, including: obtaining the public library file version of the exemption file to be transferred in the public library and the local file version of the exemption file to be transferred locally based on the transferable exemption file information; when the local file version is inconsistent with the public library file version, a transfer instruction for performing transfer processing on the exemption file to be transferred in the public library file version is generated, and an import instruction for importing the transferred exemption file to be transferred into the current level is generated; when the local file version is consistent with the public library file version, an import instruction for importing the exemption file to be transferred in the local file version into the current level is generated.
[0087] Specifically, the embodiments of this application can realize the automated generation of relevant instructions acting on the quality inspection tool. Taking the relevant instructions as including transfer instructions and import instructions as an example, the transfer instruction can optionally be the waiver promotion instruction that calls the RTL quality inspection tool. Taking the waiver file information that can be transferred as a list of waiver files to be transferred (e.g., a list of waiver files to be promoted) as an example, after the list of waiver files to be promoted is generated, the process can generate waiver promotion instructions and import instructions to be provided to the RTL quality check tool one by one.
[0088] In this embodiment, the process is based on the requirements of RTL quality inspection tools and outputs related instructions in a standardized manner. Even if the RTL quality inspection tool is replaced, the output instruction content of the process can be updated while maintaining the process structure, so as to realize the replacement of the inspection tool. The process is scalable and easy to maintain.
[0089] The process can obtain the public library version of the exemption file to be transferred in the public library (e.g., the version number in the public library) and the local file version of the exemption file to be transferred locally, i.e., the file version of the local path, based on the transferable exemption file information (e.g., file path).
[0090] When the local file version is inconsistent with the public library file version, the flow can generate a transfer instruction for performing transfer processing on the exemption file to be transferred for the public library file version, and an import instruction for importing the transferred exemption file to be transferred into the current level. In this embodiment of the application, the flow supports automatic comparison between the public library file version and the local file version, and by default uses the version in the public library as the benchmark to correct the local version file, thereby improving the reliability of file use.
[0091] When the local file version matches the public library file version, the flow can generate an import instruction to import the exemption file to be transferred in the local file version into the current level. Specifically, if the local file version matches the public library file version, the exemption file version comparison is considered successful. The flow supports omitting the transfer processing action and directly calling the exemption file of the local file version (i.e., the waiver processed locally). When performing RTL quality checks multiple times at the same level in the same folder, this enhances the inheritability of local files and improves check efficiency.
[0092] Regarding the generation of waiver promotion commands, such as Figure 7As shown, the transfer instruction uses the waiver promotion instruction, the transferable waiver file information uses the list of waiver files to be transferred (e.g., the list of waiver files to be promoted), and the flow is the waiver promotion flow. Taking the waiver waiver list as an example, the list of waiver files to be promoted includes waiver files with hierarchical identifiers of module_A and module_B. For the waiver file with hierarchical identifier of module_A, its local file version in the local path is waiver_promotion_A_tag_n, and its public library file version in the public library is waiver_A_tag_n, where tag_n can refer to the version number. For the waiver file with hierarchical identifier of module_B, its public library file version in the public library is waiver_B_tag_m, where tag_m can refer to the version number.
[0093] For the exemption file to be transferred, identified by level `module_A`, since its version in the public library file in the public library matches the version number of its version in the local path, an import instruction can be generated to import the local version of the exemption file into the current level. Figure 7 The import of `waiver_promotion_A_tag_n` is performed. For the exemption file to be transferred with the level identifier `module_B`, since there is no local file version corresponding to the public library file version `waiver_B_tag_m`, i.e., the local file version is inconsistent with the public library file version, a transfer instruction can be generated to perform promotion on the exemption file `waiver_B_tag_m` of the public library file version (i.e., promote `waiver_B_tag_m` to generate the `waiver_promotion_B_tag_m` file), and an import instruction can be generated to import the transferred exemption file (i.e., the `waiver_promotion_B_tag_m` file) into the current level. Figure 7 Import waiter_promotion_B_tag_n in the middle.
[0094] Furthermore, the process can generate a local promotion instruction file to store the analyzed and organized waiver promotion instructions and import instructions. For example, the process can sequentially retrieve the version number of the file at the current path in the public library and compare it to see if a waiver promotion file for the same sub-part already exists with the same version. If the process determines that the version of the current sub-part matches, it indicates that the waiver promotion has already been completed locally for the current file version, and there is no need to re-promote that sub-part. The promotion instruction file only generates an import instruction for the waiver after the sub-part's promotion, pointing to the local target file. If the local sub-part's waiver and the promoted file do not exist or their versions are inconsistent with the public library, then the instruction file generates a waiver promotion instruction for that sub-part using the original version from the public library. The promoted waiver file is stored in the local directory, and an instruction to import the promoted waiver file is generated.
[0095] In one embodiment, the transferable exemption file information includes auxiliary information of the exemption file to be transferred; step S106 may include: when the auxiliary information indicates that the exemption file to be transferred is a whitelisted file, confirming the transfer method of the exemption file to be transferred according to the exemption guidance information; wherein, the transfer method includes whether to perform transfer processing on the exemption file to be transferred; the transfer processing is used to make the exemption file to be transferred adapt to the current level of invocation.
[0096] Specifically, this application also supports configuration file whitelists. The whitelist allows a flow to skip comparing public library and local file versions for one or more sub-sections, using the exemption guidance information input into the flow as the sole reference. The flow then determines the method of transmitting the exemption file based on the exemption guidance information. The whitelist feature makes the use cases for flows more flexible.
[0097] In one embodiment, the method of transmitting the exemption file to be transmitted is determined according to the exemption guidance information, including: generating at least one of a transmission instruction and an import instruction according to the exemption guidance information; wherein the transmission instruction is used to instruct the exemption file to be transmitted to perform transmission processing, and the import instruction is used to instruct the exemption file to be transmitted or the exemption file to be transmitted after transmission processing to be imported into the current level.
[0098] Specifically, regarding the method of transmitting the exemption documents to be transmitted as confirmed in the exemption guidance information, the process can selectively generate transmission instructions and import instructions based on the file types specified in the exemption guidance information.
[0099] The above file transfer method has configurable options, such as subset directory index / version comparison whitelist, which improves the ease of use of the process and expands the application scenarios of the process.
[0100] In one exemplary embodiment, such as Figure 8 As shown, a quality inspection method is provided. Taking the exemption file corresponding to the sub-part of the method as an example, which is obtained by the above-mentioned file transfer method, the method may include the following steps S302 to S304.
[0101] Step S302: Obtain the RTL code-related files and the exemption files corresponding to the sub-parts of the current level.
[0102] For details regarding the exemption documents corresponding to the sub-parts of the current level, please refer to the previous description; they will not be repeated here.
[0103] Specifically, the RTL quality check tool (referred to as the tool) can obtain RTL code-related files and exemption files corresponding to the sub-parts of the current level; RTL code-related files can refer to RTL code-related files, which are used by the tool to actually perform RTL quality checks.
[0104] Step S304: Based on the RTL code-related files and the exemption files corresponding to the sub-parts, perform an RTL quality check to obtain the RTL quality check result for the current level.
[0105] Specifically, the RTL quality inspection tool can perform RTL quality inspections based on RTL code-related files and exemption files corresponding to sub-parts, thereby obtaining the RTL quality inspection results for the current level.
[0106] In some embodiments, the method further includes uploading one or more of the following to a public library: RTL code-related files, RTL quality check results for the current level, exemption files for the current level, and exemption guidance information.
[0107] In one embodiment, the method further includes: storing one or more of the following locally: transferable exemption file information, transfer-processed exemption file to be transferred, and transfer instructions.
[0108] Regarding the aforementioned storage locally / upload to a public library, this application proposes a management method for RTL quality inspection exemption files. In large-chip scenarios, taking the process from the block level to the top level as an example, RTL quality inspection is usually completed collaboratively by multiple engineers, requiring explicit management of files between each level. During the exemption file transfer process, the transfer of exemption files from the block level to the top level is also a necessary condition for flow execution. Therefore, adhering to the exemption file management method is essential to improve flow execution efficiency.
[0109] In this embodiment, the files required by the flow can be divided into two categories: files from a public repository and files located on a local path. The public repository stores conclusive documents from each level after RTL quality checks have been completed. These documents have been verified for quality and may be used in higher-level RTL quality checks, such as RTL code, reports, waiver documents, and waiver guidance information (e.g., waiver promotion guidance documents, or simply waiver promotion guidance). Files on the local path are temporary files stored before the RTL quality check is complete. These files are either input files that the flow can accept or stage files generated by the flow and only effective in this specific RTL quality check.
[0110] For example, the necessary input files for a flow include at least: a waiver promotion guide file and RTL code-related files. The RTL code-related files are used by the tool to actually perform RTL quality checks. In the use case, this file needs to be checked and verified before it can be uploaded to the public library; therefore, as input to the flow, this file can be executed using a local file. Similarly, the waiver promotion guide file can also be executed using a local file.
[0111] The cleanup phase can read the content of the waiver promotion guidelines and then perform configurable indexing of subset directories. The purpose of subset directory indexing is to completely search for waiver files that may be referenced by sub-sections. Therefore, the sub-sections need to complete the checks and upload them to the current level for use. The subset directory index of the current level will only index files on the public library. The list of waivers to be promoted generated in this phase is only used in this RTL quality check, and is generated only in the local path, without needing to be uploaded to the public library.
[0112] During the waiver promotion instruction generation phase, it's necessary to compare the version of the exemption file for that sub-part in the public library with the version of the exemption file for that sub-part after promotion on the local path. The exemption file for that sub-part after promotion at this level will not be used by other levels and may be frequently iterated; therefore, it is only stored locally and does not need to be uploaded to the public library. The waiver promotion instructions generated in this phase are only invoked during this RTL quality check and are generated only on the local path, without needing to be uploaded to the public library.
[0113] After completing the RTL quality check, it is necessary to upload the RTL-related documents, exemption documents, and waiver promotion guidelines to the public repository.
[0114] To further illustrate this application, a specific example is provided below, such as... Figure 9 As shown, users can input RTL-related files / exemption files and configure flow options. The flow then reads the waiver promotion guidelines and configures a subset directory index. It searches for exemption files within the subset in the public repository line by line until the subset directory index is complete, generating a list of exemption files to be promoted (the waiver promotion list). The flow reads the waiver promotion list line by line. If no whitelist is configured, it compares the versions of the exemption files locally / in the public repository. Once the version comparison is complete, or if a whitelist is configured, it generates a promotion instruction (waiverpromotion instruction) to perform RTL quality checks.
[0115] In this embodiment, the process supports passing exemption files from sub-parts to the current level based on RTL quality inspection tools, reducing the workload of manually re-checking exemptable items and conforming to the use case of large-scale chip RTL quality inspection. The process maintains a configurable subset exemption directory index based on public library file versions, enhancing the inheritability of public library exemption files from the block level to the top level. The process can directly / indirectly reference exemption files on public libraries that have been verified through RTL quality inspection, simplifying the file preparation process and improving inspection efficiency.
[0116] Furthermore, the process supports automatic comparison of public library file versions and local file versions, using the version in the public library as the default benchmark to correct local versions and improve the reliability of file usage. Moreover, when the version comparison of the exempted file passes after local promotion or when the configuration file is whitelisted, the process can omit the exemption promotion action and directly call the locally promoted exempted file. This enhances the inheritability of local files and improves inspection efficiency when performing RTL quality checks multiple times at the same level in the same folder.
[0117] The workflow, based on the requirements of RTL quality inspection tools, outputs a standardized waiver promotion instruction file. Even if the RTL quality inspection tool is changed, the content of the output waiver promotion instruction file can be updated while maintaining the workflow structure, thus enabling tool replacement. The workflow is scalable and easy to maintain. It offers configurable options, such as subset directory indexes and version comparison whitelists, improving usability and expanding its application scenarios. Based on the workflow and common library tools, a complete file management method is proposed to further enhance its application scenarios.
[0118] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.
[0119] Based on the same inventive concept, this application also provides a file transfer apparatus for implementing the file transfer method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more file transfer apparatus embodiments provided below can be found in the limitations of the file transfer method described above, and will not be repeated here.
[0120] In one exemplary embodiment, such as Figure 10 As shown, a file transfer device is provided, the device comprising:
[0121] The guidance information acquisition module 801 is used to acquire exemption guidance information; the exemption guidance information is used to indicate the exemption file corresponding to the sub-part of the current level;
[0122] The information processing module 802 is used to process the exemption guidance information to obtain transferable exemption document information;
[0123] The file transfer module 803 is used to transfer the exemption file corresponding to the sub-part to the current level based on the transferable exemption file information.
[0124] In one embodiment, the information processing module 802 is used to verify the authenticity of the exemption guidance information; if it is authentic, the exemption guidance information is expanded and deduplicated to obtain transferable exemption document information.
[0125] In one embodiment, the exemption guidance information includes the hierarchical identifier of the sub-part and the file path of the exemption file corresponding to the sub-part; the transferable exemption file information includes the hierarchical identifier and file path of the exemption file to be transferred; the information processing module 802 includes: a directory indexing module, used to search for the corresponding subset directory of exemption guidance in the public library according to the hierarchical identifier of the sub-part, until the subset directory indexing is completed; and a deduplication module, used to deduplicate the hierarchical identifier of the sub-part and the file path of the exemption file corresponding to the sub-part, as well as the hierarchical identifier and the file path of the exemption file under the subset directory, to obtain the hierarchical identifier and file path of the exemption file to be transferred.
[0126] In one embodiment, the exemption guidance information takes the form of at least one information format, such as a document or a list; the transferable exemption document information takes the form of at least one information format, such as a document or a list.
[0127] In one embodiment, the file transfer module 803 is used to compare the versions of the exemption file to be transferred based on the transferable exemption file information, and to determine the transfer method of the exemption file to be transferred according to the result of the version comparison; wherein, the transfer method includes the version of the exemption file to be transferred, and whether to perform transfer processing for the exemption file to be transferred; the transfer processing is used to make the exemption file to be transferred adapt to the current level of calling.
[0128] In one embodiment, the file transfer module 803 is configured to obtain, based on the transferable exemption file information, the public library file version of the exemption file to be transferred in the public library and the local file version of the exemption file to be transferred locally; when the local file version is inconsistent with the public library file version, a transfer instruction is generated to perform transfer processing on the exemption file to be transferred in the public library file version, and an import instruction is generated to import the transferred exemption file to be transferred into the current level; when the local file version is consistent with the public library file version, an import instruction is generated to import the exemption file to be transferred in the local file version into the current level.
[0129] In one embodiment, the transferable exemption file information includes auxiliary information of the exemption file to be transferred; the file transfer module 803 is used to confirm the transfer method of the exemption file to be transferred according to the exemption guidance information when the auxiliary information indicates that the exemption file to be transferred is a whitelisted file; wherein, the transfer method includes whether to perform transfer processing on the exemption file to be transferred; the transfer processing is used to adapt the exemption file to be transferred to the current level of invocation.
[0130] In one embodiment, the method of transmitting the exemption file to be transmitted is determined according to the exemption guidance information, including: generating at least one of a transmission instruction and an import instruction according to the exemption guidance information; wherein the transmission instruction is used to instruct the exemption file to be transmitted to perform transmission processing, and the import instruction is used to instruct the exemption file to be transmitted or the exemption file to be transmitted after transmission processing to be imported into the current level.
[0131] Based on the same inventive concept, this application also provides a quality inspection apparatus for implementing the quality inspection method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more quality inspection apparatus embodiments provided below can be found in the limitations of the quality inspection method described above, and will not be repeated here.
[0132] In one exemplary embodiment, such as Figure 11 As shown, a quality inspection device includes:
[0133] The file acquisition module 901 is used to acquire RTL code-related files and exemption files corresponding to the sub-parts of the current level; wherein, the exemption files corresponding to the sub-parts are obtained using the file transfer method described above;
[0134] The quality inspection module 902 is used to perform RTL quality inspection based on RTL code-related files and exemption files corresponding to sub-parts, and obtain the RTL quality inspection results of the current level.
[0135] In one embodiment, the method further includes uploading one or more of the following to a public library: RTL code-related files, RTL quality check results for the current level, exemption files for the current level, and exemption guidance information.
[0136] In one embodiment, the method further includes storing one or more of the following locally: transferable exemption file information, transfer-processed exemption file to be transferred, and transfer instructions.
[0137] Each module in the above-mentioned device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.
[0138] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 12 As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When executed by the processor, the computer program implements a file transfer method / quality check method. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.
[0139] Those skilled in the art will understand that Figure 12The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0140] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.
[0141] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.
[0142] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
[0143] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.
[0144] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0145] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A file delivery method, characterized by, The method comprises: acquiring exemption guide information; the exemption guide information is used to indicate an exemption file corresponding to a subpart of a current level; organizing the exemption guide information to obtain deliverable exemption file information; the deliverable exemption file information comprises relevant information of an exemption file that is confirmed to be deliverable to the subpart of the current level after organization; the exemption guide information comprises a level identifier of the subpart and a file path of the exemption file corresponding to the subpart; the deliverable exemption file information comprises a level identifier and a file path of a to-be-delivered exemption file; delivering the exemption file corresponding to the subpart to the current level based on the deliverable exemption file information; wherein delivering the exemption file corresponding to the subpart to the current level based on the deliverable exemption file information comprises: performing version comparison of the to-be-delivered exemption file based on the deliverable exemption file information, and confirming a delivery mode of the to-be-delivered exemption file according to a result of the version comparison; the delivery mode comprises a version of the to-be-delivered exemption file and whether to perform a delivery process on the to-be-delivered exemption file; the delivery process is used to adapt the to-be-delivered exemption file to a call of the current level; performing version comparison of the to-be-delivered exemption file based on the deliverable exemption file information, and confirming a delivery mode of the to-be-delivered exemption file according to a result of the version comparison, comprises: acquiring a common library file version of the to-be-delivered exemption file in a common library and a local file version of the to-be-delivered exemption file locally based on the deliverable exemption file information; when the local file version is inconsistent with the common library file version, generating a delivery instruction for performing the delivery process on the to-be-delivered exemption file of the common library file version, and generating an import instruction for importing the to-be-delivered exemption file after the delivery process into the current level; when the local file version is consistent with the common library file version, generating an import instruction for importing the to-be-delivered exemption file of the local file version into the current level.
2. The method of claim 1, wherein, organizing the exemption guide information to obtain deliverable exemption file information comprises: confirming authenticity of the exemption guide information; if authentic, performing expansion and deduplication on the exemption guide information to obtain the deliverable exemption file information.
3. The method of claim 2, wherein, performing expansion and deduplication on the exemption guide information to obtain the deliverable exemption file information comprises: finding a corresponding subset directory of exemption guide in a common library according to the level identifier of the subpart until subset directory indexing is completed; performing deduplication on the level identifier of the subpart, the file path of the exemption file corresponding to the subpart, and the level identifier and the file path of the exemption file under the subset directory to obtain the level identifier and the file path of the to-be-delivered exemption file.
4. The method of claim 1, wherein, The exemption guide information adopts at least one of a file and a list; the deliverable exemption file information adopts at least one of a file and a list.
5. The method according to any one of claims 1 to 4, characterized in that, The deliverable exemption file information comprises auxiliary information of the to-be-delivered exemption file; transferring the exempt file corresponding to the sub-part to the current level based on the transferable exempt file information, including: when the auxiliary information indicates that the exempt file to be transferred is a white list file, determining a transfer mode of the exempt file to be transferred according to the exempt guide information; wherein the transfer mode includes whether to perform a transfer process on the exempt file to be transferred; the transfer process is used to adapt the exempt file to be transferred to the call of the current level.
6. The method of claim 5, wherein, According to the exempt guide information, the transfer mode of the exempt file to be transferred is determined, including: According to the exempt guide information, at least one of the transfer instruction and the import instruction is generated; wherein the transfer instruction is used to instruct to perform a transfer process on the exempt file to be transferred, and the import instruction is used to instruct to import the exempt file to be transferred or the exempt file to be transferred after the transfer process into the current level.
7. A quality inspection method characterized by, The method includes: obtaining the RTL code related file and the exempt file corresponding to the sub-part of the current level; wherein the exempt file corresponding to the sub-part is obtained by using the file transfer method in any one of claims 1 to 6; based on the RTL code related file and the exempt file corresponding to the sub-part, performing RTL quality inspection to obtain the RTL quality inspection result of the current level.
8. The method of claim 7, wherein, The method further includes: uploading one or more of the RTL code related file, the RTL quality inspection result of the current level, the exempt file of the current level, and the exempt guide information to a public library.
9. The method of claim 7, wherein, The method further includes: saving one or more of the transferable exempt file information, the exempt file to be transferred after the transfer process, and the transfer instruction locally.
10. A file delivery apparatus, characterized by comprising: The device includes: an exempt guide information acquisition module, configured to acquire exempt guide information; the exempt guide information is used to indicate the exempt file corresponding to the sub-part of the current level; an information arrangement module, configured to arrange the exempt guide information to obtain transferable exempt file information; the transferable exempt file information includes the related information of the exempt file that can be transferred to the sub-part of the current level after arrangement; the exempt guide information includes the level identifier of the sub-part and the file path of the exempt file corresponding to the sub-part; the transferable exempt file information includes the level identifier and the file path of the exempt file to be transferred; a file transfer module, configured to transfer the exempt file corresponding to the sub-part to the current level based on the transferable exempt file information; the file transfer module is configured to perform version comparison of the exempt file to be transferred based on the transferable exempt file information, and determine a transfer mode of the exempt file to be transferred according to the result of the version comparison; the transfer mode includes the version of the exempt file to be transferred, and whether to perform a transfer process on the exempt file to be transferred; the transfer process is used to adapt the exempt file to be transferred to the call of the current level. The file delivery module is configured to: based on the deliverable exemption file information, acquire a public library file version of the to-be-delivered exemption file in a public library and a local file version of the to-be-delivered exemption file locally; when the local file version is inconsistent with the public library file version, generate a delivery instruction for performing the delivery processing on the to-be-delivered exemption file in the public library file version, and generate an import instruction for importing the to-be-delivered exemption file after the delivery processing into the current level; and when the local file version is consistent with the public library file version, generate an import instruction for importing the to-be-delivered exemption file in the local file version into the current level.
11. A quality inspection apparatus characterized by comprising: The apparatus comprises: a file acquisition module configured to acquire RTL code related files and exemption files corresponding to a subpart of a current level; wherein the exemption files corresponding to the subpart are obtained by using the file delivery method of any one of claims 1 to 6; a quality inspection module configured to perform RTL quality inspection based on the RTL code related files and the exemption files corresponding to the subpart, to obtain an RTL quality inspection result of the current level.
12. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor, when executing the computer program, implements the steps of the method of any one of claims 1 to 9.
13. A computer readable storage medium having stored thereon a computer program, characterized in that The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 9.
14. A computer program product comprising a computer program, characterized in that, The computer program, when executed by the processor, implements the steps of the method of any one of claims 1 to 9.
Citation Information
Patent Citations
Chip file quality management method and device, electronic equipment and storage medium
CN118734791A
Code checking method and device, equipment and storage medium
CN120705012A