CN112685277B

CN112685277B - Warning information checking method and device, electronic equipment and readable storage medium

Info

Publication number: CN112685277B
Application number: CN202011643887.8A
Authority: CN
Inventors: 沈旭; 王芳
Original assignee: Haiguang Information Technology Co Ltd
Current assignee: Haiguang Information Technology Co Ltd
Priority date: 2020-12-31
Filing date: 2020-12-31
Publication date: 2023-01-24
Anticipated expiration: 2040-12-31
Also published as: CN112685277A

Abstract

The application provides a warning information checking method, a warning information checking device, an electronic device and a readable storage medium, wherein the method comprises the following steps: simulating the design of a target chip in the current verification environment to obtain a simulation log file; traversing the simulation log file to extract target warning information in the simulation log file; when the warning information list does not have warning information corresponding to the target warning information, writing the target warning information into the warning information list; when warning information corresponding to the target warning information exists in the warning information list and the target warning information carries a set identifier, adding a verification identifier for the corresponding warning information in the warning information list to update the warning information list; and repeating the steps until all the warning messages in the warning message list have the verification marks. According to the method in the embodiment, the checking efficiency of the warning information can be improved, and meanwhile, the accuracy of the warning information can also be improved.

Description

Warning information checking method and device, electronic equipment and readable storage medium

Technical Field

The present application relates to the field of chip design technologies, and in particular, to a warning information checking method and apparatus, an electronic device, and a readable storage medium.

Background

In the current chip design stage, before a physical chip is manufactured, each function of the chip design is verified by means of simulation. Some warning information may be present in the simulation result of the chip, for example, the warning information may indicate that an abnormal condition has occurred, but has not yet reached a wrong step; as another example, the warning message may also be a degradation of an error of a particular checker to a warning under certain circumstances. In the subsequent stage of chip design, the warning information in the simulation result needs to be checked, so that the accuracy of the output warning information is ensured.

However, with the increasing and complex chip design scale, the verification environment is more and more complex, and under the condition of more and more test cases, the amount of warning information is also larger, and the current warning information is checked by manual work, so that the efficiency is relatively low.

Disclosure of Invention

The application aims to provide a warning information checking method, a warning information checking device, an electronic device and a readable storage medium, which can solve the problem of low efficiency caused by manual checking of warning information.

In a first aspect, the present invention provides a method for checking warning information, including:

simulating the design of a target chip in the current verification environment to obtain a simulation log file;

traversing the simulation log file to extract target warning information in the simulation log file;

comparing the target warning information with a current warning information list;

when the warning information list does not contain warning information corresponding to the target warning information, writing the target warning information into the warning information list so as to update the warning information list;

when the target warning information carries a set identifier and warning information corresponding to the target warning information exists in the warning information list, adding a verification identifier for the corresponding warning information in the warning information list to update the warning information list;

and repeating the steps until all the warning messages in the warning message list have verification marks.

In an optional embodiment, the comparing the target warning information with a warning information list includes:

comparing a designated field in the target warning information with each item of warning information in the warning information list;

and when the warning information containing the specified field exists in the warning information list, representing that the warning information corresponding to the target warning information exists in the warning information list.

In the above embodiment, when updating the warning information list, based on different requirements, a fuzzy matching method may be adopted, and for the warning information of the same type, for example, the warning information including the specified field, the updating may be performed once, so that the checking amount of the warning information may be reduced, and the checking efficiency may be improved.

In an alternative embodiment, a field is defined in the warning message; the comparing the specified field in the target warning information with each item of warning information in the warning information list comprises:

comparing fields except the limited fields in the target warning information with fields except the limited fields in each item of warning information in the warning information list;

when the warning information list has the warning information which is the same as the fields of the target warning information except the limited fields, the warning information list is characterized that the warning information corresponding to the target warning information exists.

In an optional embodiment, each piece of warning information includes multiple pieces of information, the multiple pieces of information include a warning entity and path information, and the defined field is a first field of the warning entity, or the defined field is a second field of the path information.

In the above embodiment, the warning information in the same test case can be regarded as the same type of warning information, so that the warning information in the same test case can be checked as the same warning information, the number of warning information that needs to be checked can be reduced, and the checking efficiency can be improved. The warning entity is used for bearing main potential danger information of warning, and the warning information is classified based on the warning entity, so that the warning information which represents the same potential danger information is not checked repeatedly, the checking of the repeated warning information can be reduced, and the checking efficiency is improved.

In an optional embodiment, each piece of warning information includes multiple pieces of information, the multiple pieces of information include a warning entity and path information, the warning entity includes a first field, and the path information includes a second field; the comparing the specified field in the target warning information with each item of warning information in the warning information list comprises:

comparing fields of the target warning information except the first field and the second field with fields of various items of warning information in the warning information list except the first field and the second field;

when the warning information list has the warning information which is the same as the fields of the target warning information except the first field and the second field, the warning information list is characterized to have the warning information corresponding to the target warning information.

In an alternative embodiment, the comparing the target warning information with a warning information list includes:

comparing all fields in the target warning information with all warning information in the warning information list;

and when the warning information list has the warning information which is the same as the target warning information, representing that the warning information corresponding to the target warning information exists in the warning information list.

In the above embodiment, when the warning information list is updated, based on different requirements, a more comprehensive warning information can be updated to the warning information list in an accurate matching manner, so that various warning information can be more comprehensively covered, and the inspection content is more comprehensive.

In an alternative embodiment, the method further comprises: and when the warning information exists in the warning information list, updating the warning output field in the current verification environment by using the set identifier according to the warning information in the current warning information list so as to obtain the current verification environment.

In the above embodiment, the verification environment is marked by adding a set scale based on the obtained warning information list, so that the determined current verification environment can be adapted to the checking state of the current warning information, and the checked warning information and the unchecked warning information can be more conveniently determined.

In an optional embodiment, the updating, according to the warning information in the current warning information list, the warning output field in the current verification environment using the set identifier to obtain the current verification environment includes:

if the first warning information in the current warning information list is correct warning information, adding the set identifier to a code for outputting the first warning information in the current verification environment so as to update the verification environment;

and if the second warning information in the current warning information list is wrong warning information, changing a code for outputting the second warning information in the current verification environment so as to update the verification environment.

In the above embodiment, for the correct warning information, the setting flag may be added to the code corresponding to the output warning information, so that the warning information with the setting flag may be output when the corresponding code is simulated again, and the warning information that has been checked here may be distinguished, thereby avoiding repeated checking of the correct warning information.

and if the third warning information in the current warning information list is warning information obtained by dynamic degradation, reloading an information processing function for determining the third warning information, comparing the processing logic of the information processing function with a preset user configuration table, and adding the set identifier to an information field in the information processing function to update the verification environment when the user configuration table has the same mapping relation with the processing logic.

In the above embodiment, the warning information obtained by the dynamic degradation processed by the information processing function is identified by logical matching to adapt to the labels of different scenes for outputting the warning information.

In an optional embodiment, the writing the target warning information into the warning information list to update the warning information list includes:

when the target warning information does not carry a set identifier, writing the target warning information into a warning information list;

and when the target warning information carries a set identifier, writing the target warning information into a warning information list, and adding the verification identifier to the target warning information in the warning information list.

and updating a fourth warning information output field in the current verification environment by using the set identifier when the fourth warning information in the warning information list contains the verification identifier and the fourth warning information in the current verification environment does not contain the set identifier.

In a second aspect, the present invention provides a warning information checking apparatus comprising:

the simulation log acquisition module is used for simulating the design of the target chip in the current verification environment to obtain a simulation log file;

the warning information extraction module is used for traversing the simulation log file to extract target warning information in the simulation log file;

the warning information comparison module is used for comparing the target warning information with a current warning information list;

a first list updating module, configured to, when there is no warning information corresponding to the target warning information in the warning information list, write the target warning information into the warning information list to update the warning information list;

and the second list updating module is used for adding a verification identifier to the corresponding warning information in the warning information list to update the warning information list when the warning information corresponding to the target warning information exists in the warning information list and the target warning information carries a set identifier.

In a third aspect, the present invention provides an electronic device comprising: a processor, a memory storing machine readable instructions executable by the processor, the machine readable instructions when executed by the processor perform the steps of the method of any of the preceding embodiments when the electronic device is run.

In a fourth aspect, the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method according to any one of the preceding embodiments.

The beneficial effects of the embodiment of the application are that: by automatically extracting the warning information in the simulation log file in a traversal mode, the warning information output by current simulation can be quickly obtained; and updating the warning information list based on the warning information in the simulation log file, so that the warning information without the verification identifier in the warning information list can be gradually reduced until all the warning information in the warning information list carries the verification identifier, and the warning information is checked one by one. The warning information can be quickly checked through the process, so that the workload required for checking the warning information is reduced, and the warning information can be accurately checked.

Drawings

To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.

Fig. 1 is a block diagram of an electronic device according to an embodiment of the present disclosure.

Fig. 2 is a flowchart of a warning information checking method according to an embodiment of the present application.

Fig. 3 is a flowchart of a warning information checking method according to an embodiment of the present application.

Fig. 4 is a schematic functional block diagram of a warning information checking apparatus according to an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.

Regarding the inspection of the warning information for the chip simulation phase, the simulation log file of the test case is generally searched by a grep command, and then the warning information is screened by a human line-by-line review method, which may have the following disadvantages: 1) The warning information is related to the number of the test cases, and the more the number of the test cases is, the more the warning information needs to be checked, so that the checking workload is huge; 2) Similar warning information is difficult to process uniformly due to the fact that the similar warning information is located at different positions and at different times, for example, even if the same warning information comes from the same checker, the similar warning information is considered to be different due to different reported use cases and different instantiated verification components, and manual review is required to be repeated. Based on the above deficiency of the review of the warning information, the embodiments of the present application provide a warning information inspection method, apparatus, electronic device and readable storage medium, which can relatively alleviate the above problems, and are described below by several embodiments.

Example one

To facilitate understanding of the present embodiment, first, an electronic device that executes the warning information checking method disclosed in the embodiments of the present application will be described in detail.

As shown in fig. 1, is a block schematic diagram of an electronic device. The electronic device 100 may include a memory 111, a memory controller 112, a processor 113, a peripheral interface 114, an input-output unit 115, and a display unit 116. It will be understood by those of ordinary skill in the art that the structure shown in fig. 1 is merely exemplary and is not intended to limit the structure of the electronic device 100. For example, electronic device 100 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The aforementioned components of the memory 111, the memory controller 112, the processor 113, the peripheral interface 114, the input/output unit 115 and the display unit 116 are electrically connected to each other directly or indirectly, so as to implement data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The processor 113 is used to execute the executable modules stored in the memory.

The Memory 111 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 111 is configured to store a program, and the processor 113 executes the program after receiving an execution instruction, and the method executed by the electronic device 100 defined by the process disclosed in any embodiment of the present application may be applied to the processor 113, or implemented by the processor 113.

The processor 113 may be an integrated circuit chip having signal processing capability. The Processor 113 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The peripheral interface 114 couples various input/output devices to the processor 113 and memory 111. In some embodiments, the peripheral interface 114, the processor 113, and the memory controller 112 may be implemented in a single chip. In other examples, they may be implemented separately from each other.

The input/output unit 115 is used to provide input data to the user. The input/output unit 115 may be, but is not limited to, a mouse, a keyboard, and the like.

The display unit 116 provides an interactive interface (e.g., a user operation interface) between the electronic device 100 and the user or is used for displaying image data to the user for reference. In this embodiment, the display unit may be a liquid crystal display or a touch display. In the case of a touch display, the display can be a capacitive touch screen or a resistive touch screen, which supports single-point and multi-point touch operations. The support of single-point and multi-point touch operations means that the touch display can sense touch operations simultaneously generated from one or more positions on the touch display, and the sensed touch operations are sent to the processor for calculation and processing.

The display unit 116 may be used to display data generated during the warning information inspection process. For example, a warning information list or the like may be displayed.

The electronic device 100 in this embodiment may be configured to perform each step in each method provided in this embodiment. The implementation of the warning information checking method is described in detail below by means of several embodiments.

Example two

Please refer to fig. 2, which is a flowchart of a warning message checking method according to an embodiment of the present disclosure. The specific process shown in fig. 2 will be described in detail below.

Step 201, simulating the target chip design in the current verification environment to obtain a simulation log file.

For example, the current verification environment may include multiple verification components and multiple test cases.

In this embodiment, step 201 may simulate multiple test cases in the verification environment to obtain simulation log files, respectively.

Step 202, traversing the simulation log file to extract the target warning information in the simulation log file.

Step 203, comparing the target warning information with a current warning information list.

Optionally, before step 203, a pre-configured comparison rule may also be obtained.

For example, the comparison rule may be pre-stored in a configuration file, the configuration file is obtained from a storage space of the configuration file, and the comparison rule is obtained from the configuration file.

The contrast mode may also be set by the user, for example. For example, an operation interface may be provided, according to which a comparison rule input by a user is received.

In one embodiment, step 203 may: and comparing a specified field in the target warning information with each item of warning information in the warning information list. And when the warning information containing the specified field exists in the warning information list, representing that the warning information corresponding to the target warning information exists in the warning information list.

In the above embodiment, when the comparison of the warning information is performed, a part of the fields in the warning entity are obfuscated, so that when matching is performed, the part of the fields in the warning entity can be ignored.

Illustratively, a defined field may be included in the warning information; fields other than the limited field in the target warning information may be compared with fields other than the limited field in each item of warning information in the warning information list; when the warning information which is the same as the fields of the target warning information except the limited fields exists in the warning information list, the warning information which corresponds to the target warning information exists in the warning information list.

In this embodiment, the comparison rule may include a criterion for determining similarity of the warning messages. For example, the criteria for determining that the warning messages are similar may include: ignoring differences in time; as another example, the criteria for determining that the warning messages are similar may include: ignoring differences in test cases; as another example, the criterion for determining similarity of warning information may include: ignoring differences in alert entities, etc.

Each piece of warning information comprises a plurality of pieces of information, and the plurality of pieces of information comprise warning entities, path information, warning time and the like.

Illustratively, the above-mentioned restricted field may be a first field of the alert entity.

Illustratively, the above-mentioned restricted field may be a second field of the path information.

Illustratively, the above-mentioned restricted field may be a first field of the warning entity and a second field of the path information.

Illustratively, the designated fields described above include fields other than the first field, and in this example, the difference in the first field is ignored. Step 203 may comprise: comparing fields except the first field in the target warning information with fields except the first field in each item of warning information in the warning information list; when the warning information list has the warning information which is the same as the fields of the target warning information except the first field, the warning information list is characterized to have the warning information corresponding to the target warning information.

In one example, if the warning entities of the target warning message are: PIPE data mismatched, expected: BC, received: E1. And the preset fuzzy matching rule is to fuzzy process the specific warning information in the warning entity. At this time, if the warning entity having a piece of warning information in the warning information list is: PIPE data mismatched, expected: AA, received: BB. In this example, the first fields of the target warning information are "BC" and "E1", and the first fields of the warning information in the warning information list are "AA" and "BB". Since the fields "PIPE data mismatch, expected" and "received" in the target warning information are the same as the corresponding fields in the warning information list, and only "BC" and "E1" are different, it may be determined that the warning entity of the item of warning information in the warning information list successfully matches the warning entity of the target warning information, and if the other fields of the target warning information are the same as the other fields of the warning information in the warning information list, it indicates that the warning information successfully matches the target warning information exists in the warning information list.

The above-mentioned specified field may be, for example, a field other than the second field of the path information in the warning information, and in this example, the difference of the second field of the path information is ignored. Step 203 may comprise: comparing fields except the second field in the target warning information with fields except the second field in each item of warning information in the warning information list; and when the warning information list has the warning information which is the same as the fields of the target warning information except the second field, representing that the warning information corresponding to the target warning information exists in the warning information list.

In one example, if the path information of the target warning message is: uv _ test _ top.env.pci _ uvc.lane _ uvc [0] scoreboard, and a list of alert messages exists: uv _ test _ top, env, pci _ uv, lane _ uv [2] scoreboard, wherein in the above example, the second field of the target warning message is "[0]", and the second field of the warning messages in the warning message list is "[2]". In this case, the destination warning information may be determined to have successfully matched path information with the destination warning information if the destination warning information is the same as the warning information list except that "[0]" is different from the warning information list, and may indicate that the destination warning information has successfully matched the destination warning information if the other fields of the destination warning information are the same as the other fields of the warning information in the warning information list.

Illustratively, the specified field may be a field of the warning information other than a first field of the warning entity and a second field of the path information, in which case the difference between the first field and the second field is ignored. Step 203 may comprise: comparing fields of the target warning information except the first field and the second field with fields of various items of warning information in the warning information list except the first field and the second field; when the warning information list has the warning information which is the same as the fields of the target warning information except the first field and the second field, the warning information list is characterized to have the warning information corresponding to the target warning information.

Optionally, other information may be subjected to fuzzy processing according to specific requirements, so as to adapt to the inspection requirements of different scenes on the warning information. For example, the time of the warning information may be subjected to a blurring process so that the difference in time can be ignored when comparing the target warning information with the warning information in the warning information list.

In another embodiment, if the corresponding contrast mode is not set, the mode of precise contrast may be set as a default. Illustratively, the mode of the exact comparison is that when there is a warning information identical to the target warning information in the warning information list, it is determined that there is a corresponding warning information in the warning information list.

Illustratively, step 203 may comprise: comparing all fields in the target warning information with all warning information in the warning information list; when the warning information list has the warning information which is the same as the target warning information, the warning information list is characterized to have the warning information corresponding to the target warning information; and when the warning information which is completely the same as the target warning information does not exist in the warning information list, representing that the warning information which corresponds to the target warning information does not exist in the warning information list.

Information included in the warning information, and expression forms of comparison rules of the warning information are described below with some examples.

In one example, the first warning message of test case 1 is: UVM _ WARNING @422748.61[ RxData ] UVM _ test _ top, env, pcie _ uvc, lane _ uvc [0] scoreboard, PIPE data mismatch, expected: BC, received: E1.

The corresponding warning time in the first warning message of the test case 1 is "422748.61"; the path information is 'uvm _ test _ top.env.pcie _ uvc.lane _ uvc [0]. Scoreboard'; the alert entity is "PIPE data acknowledged, expected: BC, received: E1".

The second warning message of the test case 1 is: UVM _ WARNING @422748.61[ RxData ] UVM _ test _ top. Env. Pcie _ uvc. Lane _ uvc [1] scoreboard: PIPE data mismatch, expected:1C, received.

The corresponding warning time in the second item of warning information of the test case 1 is "422748.61"; the path information is 'uv _ test _ top.env.pci _ uvc.lane _ uvc [1]. Scoreboard'; the warning entity is "expected:1C, received.

The third warning message of test case 1 is UVM _ WARNING @422750.61[ RxData ] UVM _ test _ top.env.pcie _ uvc.lane _ uvc [0]. Scoreboard: PIPE data mismatch, expected:1C, received.

The corresponding warning time in the third warning message of the test case 1 is "422750.61"; the path information is 'uvm _ test _ top.env.pcie _ uvc.lane _ uvc [0]. Scoreboard'; the warning entity is "expected:1C, received.

The first warning message of test case 2 is UVM _ WARNING @314152.51[ RxData ] UVM _ test _ top, env, pci _ uvc, lane _ uvc [2]. Scoreboard: PIPE data analyzed, expected: BC, received: A8.

The corresponding warning time in the first warning message of the test case 2 is 314152.51'; the path information is 'uv _ test _ top.env.pci _ uvc.lane _ uvc [2]. Scoreboard'; the warning entities are "PIPE data analyzed, expected: BC, received: A8".

In each of the above examples, the first warning information and the second warning information of the test case 1 belong to warnings on different channels at the same time point, the first warning information and the third warning information of the test case 1 belong to warning information on different time points of the same channel, and the first warning information of the test case 2 is different from other warning information in time point, channel and warning entity.

Optionally, fuzzy matching arbitrary time points using the regular expression \ d + \\ d +; fuzzy processing of arbitrary path information using a regular expression \ d + \ for example, using channel information "[2]" in the regular expression \ d + \\ fuzzy processing path information uvm _ test _ top.env.pc _ uvc.lane _ uvc [2]. Scoreboard, we can get uvm _ test _ top.env.pc _ uvc.lane _ uvc \ d + \\ scoreboard; the warning entity is fuzzy-matched using the regular expression [0-9a-fA-F ] +, for example, PIPE data mismatch, expected: BC, received: BC and A8 in the warning entity are fuzzy-processed using the regular expression [0-9a-fA-F ] +, thus obtaining PIPE data mismatch, expected: 0-9a-fA-F ] +, received: 0-9a-fA-F ] +.

For example, the first warning message of test case 3 is: UVM _ WARNING @422748.61[ RxData ] UVM _ test _ top. Env. Pcie _ uvc. Lane _ uvc [0] scoreboard: PIPE data mismatch, expected: BC, received: E1.

Test case 3 the second warning message is: UVM _ WARNING @422748.61[ RxData ] UVM _ test _ top-env-pcie _ uvc-lane _ uvc [1] scoreboard: PIPE data mismatch, expected:1C, received.

Wherein UVM _ WARNING @ is formatting information; 422748.61 is time information; [ RxData ] is ID information; uv _ test _ top.env.pcie _ uvc.lane _ uvc [0] scoreboard and uv _ test _ top.env.pcie _ uvc.lane _ uvc [0] scoreboard are path information, PIPE data mismatch, predicted: BC, predicted: E1 and PIPE data mismatch, predicted: 1C, predicted.

Fuzzy matching can be as follows:

for the warning information, the time can be represented by a regular expression \ d + \\ d +, and the channel information in the path information can be represented by a regular expression: uv _ test _ top.env.pcie _ uvc.lane _ uvc [ \ d + ]. Scoreboard, a warning entity may be represented by the regular expression PIPE data mismatch, expected: [0-9a-fA-F ] +, received: [0-9a-fA-F ] +;

and matching the warning information with a fuzzy matching expression shown as follows to obtain a result:

UVM_WARNING@\d+\.\d+[RxData]uvm_test_top.env.pcie_uvc.lane_uvc\[\d+\].scoreboard:PIPE data mismatched,expected:[0-9a-fA-F]+,received:[0-9a-fA-F]+。

optionally, when fuzzy matching of multiple items of information is required, a regular expression containing a specific term may be adopted at a position corresponding to the multiple items of information.

For example, if any time point and any piece of path information need to be matched in a fuzzy manner, the comparison rule may include: UVM _ WARNING @ \ d \ d + \ [ RxData \ UVM _ test _ top \ env \. Pcie _ uvc \. Lane _ uvc \ d + \. Scoreboard: PIPE data mismatch, expected: BC, received: E1.

For example, if fuzzy matching is required at any time point, the comparison rule may include: UVM _ WARNING @ \ d \ d + \ [ RxData \ UVM _ test _ top v. env \ pcie _ uvc \ Lane _ uvc \ 1. Scoreboard: PIPE data mismatched, expected:1C, received.

And 204, when the warning information list does not have warning information corresponding to the target warning information, writing the target warning information into the warning information list so as to update the warning information list.

In this embodiment, the initial state of the warning information list is empty.

And after the simulation log file is traversed, updating the warning information list according to the traversed warning information.

Optionally, the warning information list may include a path of the simulation log file, a line number where the warning information is located, and specific content of the warning information.

In one example, as shown in table 1, a path of the simulated log file is represented by log file, line represents a row number where the warning information is located, and warning represents a warning entity of the warning information.

TABLE 1

log file	line	warning
			file_0	line_0	message_0
…	…	…
			file_N	line_N	message_N

For example, in the example shown in table 1, the first item of warning information is in the simulated log file _0, the first item of warning information is in the first line _0 row of the simulated log file, and the warning entity of the first item of warning information is message _0.

In an embodiment, when the target warning information does not carry a setting identifier, the target warning information is written into a warning information list.

In another embodiment, when the target warning information carries a set identifier, the target warning information is written into a warning information list, and the verification identifier is added to the target warning information in the warning information list.

Step 205, when there is warning information corresponding to the target warning information in the warning information list and the target warning information carries a set identifier, adding a verification identifier to the corresponding warning information in the warning information list to update the warning information list.

Optionally, when warning information corresponding to the target warning information exists in the warning information list, and the target warning information carries a set identifier, and the target warning information in the warning information list does not have a verification identifier, the verification identifier may be added to the corresponding warning information in the warning information list, so that the target warning information in the warning information list includes the verification identifier.

Optionally, when warning information corresponding to the target warning information exists in the warning information list, and the target warning information does not carry a set identifier, and the target warning information in the warning information list has a verification identifier, prompt information may be output. The prompt message is used to prompt the user that there may be an error in checking the current warning message.

In this embodiment, if only one simulation log file is currently obtained, in a round of production process of the warning information list, the steps 202 to 205 are repeated until the warning information in one simulation log file is traversed.

In this embodiment, if a plurality of simulation log files are currently obtained, in a round of production process of the warning information list, the steps 202 to 205 are repeated until the warning information in the plurality of simulation log files is traversed.

Alternatively, to enable more comprehensive verification of the warning information, the verification environment may be updated based on the current state of the warning information in the warning information list.

In one embodiment, an update policy of the verification environment may be generated according to the current warning information list, and the update policy records a field to be updated in the verification environment, content of the field to be updated before updating, and content of the field to be updated after updating. The update policy is for reference by a user.

In another embodiment, the automatic verification environment may be updated based on the content of each item of warning information in the current warning information list. As shown in fig. 3, the warning information checking method of the present embodiment may further include: step 206, when there is warning information in the warning information list, updating the warning output field in the current verification environment by using the set identifier according to the warning information in the current warning information list, so as to obtain the current verification environment.

Illustratively, when the fourth warning information in the warning information list contains a verification identifier and the output field of the fourth warning information in the current verification environment does not contain the setting identifier, the fourth warning information output field in the current verification environment is updated by using the setting identifier.

The first warning information is any one of the warning information lists containing the verification identifier.

In this embodiment, through the loop of step 201 to step 206, the warning information list is updated, and each warning information is gradually checked until all the warning information in the warning information list has the verification identifier.

In this embodiment, updating the warning output field in the current verification environment by using the setting identifier may be performed by adding the setting identifier at a specified position of the warning output field. For example, the specified location may be the end of the alert output field.

The warning output field may be warning information, fatal information, error information, or the like.

Illustratively, if the original severity level of a WARNING message in the WARNING message list is WARNING and an error-free message is confirmed, the original code for outputting the WARNING message in the verification environment is updated, and the original WARNING message in the code for outputting the WARNING message in the verification environment is added with a suffix "< < WARNING _ HOOK".

Illustratively, the contents of the acknowledgment error-free message include: confirming that the warning message is within expectations does not pose a real problem. Optionally, an operable interface is provided, and the confirmation message is a message received by the operable interface.

Wherein the < < WARNING _ HOOK sets the flag for one of the entries. Of course, the setting flag may be composed of other character strings.

Illustratively, if the original severity level of the warning message is FATAL or erroneous, is degraded to a warning, and after an acknowledgement-free message is obtained, the original code for outputting the warning message in the verification environment is updated, and the original FATAL message in the code for outputting the original FATAL message in the verification environment is added with a suffix "< < FATAL _ HOOK"; the original ERROR information in the code outputting the original ERROR information in the verification environment is added with a suffix "< < ERROR _ HOOK".

In the above example, < < FATAL _ HOOK and < < ERROR _ HOOK set the identification for two of them.

In this embodiment, if the set identifiers (< < WARNING _ HOOK, < < ERROR _ HOOK, and < < facial _ HOOK) are carried in the WARNING information obtained from the simulation log, it indicates that the corresponding WARNING information has already been checked, and the checking may not be performed. At this time, if there is WARNING information corresponding to the WARNING information with setting marks (< < WARNING _ HOOK, < < ERROR _ HOOK, and < < facial _ HOOK) in the WARNING information list, and the WARNING information has a verification mark, it indicates that the WARNING information has been verified.

If the target warning information obtained by the simulation log does not carry the set identifier, the corresponding warning information is not checked, and the checking is required. At this time, when the warning information corresponding to the target warning information exists in the warning information list and the warning information in the warning information list has the verification identifier, the current fuzzy matching expression is represented, a large amount of information is sent to fuzzy processing so that different warning information is considered to be the same, the current denotation has a problem, and the prompt information can be output. The prompt message is used for prompting the user that the current warning message is checked to be possible to have errors.

In one example, the verification environment for the target chip design may be built using a verification methodology. For example, a validation environment constructed by Universal Validation Methodology (UVM). Error and warning information for a verification environment built based on the universal verification methodology is typically reported by macros as follows:

`uvm_error(report_id,message)；

`uvm_warning(report_id,message)；

`uvm_fatal(report_id,message)；

wherein, the report _ id represents the unique identifier of the current information, and the message represents the corresponding error information or warning information or fatal information. Illustratively, the above report _ id can be used to distinguish different information, but since one verification component may be instantiated multiple times, it is impossible to precisely locate specific information of a target verification component using only the report _ id, and accordingly, it is necessary to locate the specific information by using the hierarchy information of the verification component in combination with the report _ id.

In the above example, when the warning output field needs to be updated based on the warning information in the warning information list, the value in the message may be updated. And adding a set identifier to the original message value to obtain an updated message.

In one embodiment, the warning information may be warning information that is directly output by a macro in the verification environment. In this embodiment, step 206 may include: if the first warning information in the current warning information list is correct warning information, adding the set identifier to a code for outputting the first warning information in the current verification environment so as to update the verification environment; and if the second warning information in the current warning information list is wrong warning information, changing a code for outputting the second warning information in the current verification environment so as to update the verification environment.

Alternatively, the determination of correctness and mistakes of the warning information may be: and receiving the marking operation of the user on each item of warning information in the warning information list, wherein the marking is used for indicating whether each item of warning information is correct warning information. Illustratively, whether each item of warning information is correct warning information is identified through the identification of the mark in each item of warning information in the warning information list. In one example, the indicia of the warning message may be divided into three categories: correct, incorrect, and pending. Wherein the correct flag indicates that the warning message is correct and does not need to be checked again; the error flag indicates that the warning message is erroneous; the pending flag indicates that the warning message is correct, but that checking is required for other test cases.

In an example, if a flag corresponding to the first warning information is a pending flag, where the pending flag indicates that the current state of the first warning information is correct, but other test cases need to be checked, the setting flag may not be added to the code for outputting the first warning information in the current verification environment.

In another example, if the flag corresponding to the first WARNING message is correct, the current verification environment adds a suffix "< < WARNING _ HOOK" to the message in the macro for outputting the first WARNING message.

In another example, if the flag corresponding to the first warning message is an error flag, the message in the macro for outputting the first warning message in the current verification environment is upgraded to an error or downgraded to a normal message.

In one embodiment, the warning message may be a degradation of a particular checker's error to a warning under certain circumstances, thereby quickly meeting the verification objective at the time. In this embodiment, step 206 may include: and if the third warning information in the current warning information list is warning information obtained by dynamic degradation, reloading an information processing function for determining the third warning information, comparing the processing logic of the information processing function with a preset user configuration table, and adding the set identifier to an information field in the information processing function to update the verification environment when the user configuration table has the same mapping relation with the processing logic.

Illustratively, the dynamic downgrade may represent the conversion of original high-level warning information to low-level warning information in a verification environment.

In one example, an information handling function in the authentication environment may generate an entity of the type uvmreport message, which includes: object, id, version, and message. The object can determine a unique verification component, the id can determine a unique piece of information in the verification component, the security can determine the original severity level of the information, and the message represents the original information.

Illustratively, the user profile table may be as shown in table 2 below.

TABLE 2

object	id	old_severity	new_severity
				object_0	id_0	UVM_FATAL	UVM_WARNING
…	…	…	…
				object_N	id_N	UVM_ERROR	UVM_WARNING
null	id_X	UVM_ERROR	UVM_WARNING

Wherein, in the example shown in table 2, the target verification component that needs to be updated is represented by object; id represents a unique identifier of target information in the target verification component; old _ severity represents the original severity level of the information; new _ severity indicates a new information severity level specified.

For example, in table 2, the fatal information identified as id _0 in object _0 is specified to be degraded into warning information; for error information identified as id _ N in object _ N, demotion to warning information is specified; for all error information identified as id _ X in the verification component, the user specifies to downgrade it to warning information.

Exemplarily, the information processing function outputting the second warning information is reloaded to determine the processing logic obtaining the second warning information, the processing logic is compared with a user configuration table, and whether an output node corresponding to the second warning information exists, and whether the original severity level and the new severity level corresponding to the output node are the same as the processing logic obtaining the second warning information by the information processing function are judged. If the two types of messages are the same, adding a suffix "< < FATAL _ HOOK" or "< < ERROR _ HOOK" into the messages in the entities of the type uvm _ report _ message according to old _ version in the user configuration table to complete the denotation. If the output node corresponding to the second warning information does not exist in the user configuration table, or the original severity level and the new information severity level corresponding to the output node are different from the processing logic of the second warning information obtained by the information processing function, the message in the entity of the type uvm _ report _ message is not changed.

Illustratively, the output node may be represented by a verification component object and a unique identification id of the target information in the verification component.

In this embodiment, the final state of the warning information list is empty.

In the embodiment of the application, the warning information in the simulation log file is automatically extracted in a traversal mode, so that the warning information output by the current simulation can be quickly obtained; and marking the verification environment based on the obtained warning information list, so that the warning information without verification marks in the warning information list can be gradually reduced until all the warning information in the warning information list carries the verification marks, and the warning information is checked one by one. The warning information can be quickly checked through the process, so that the workload for checking the warning information is reduced, and the warning information can be accurately checked.

Further, since the test case has randomness, there is a possibility that the test case has warning information in one regression, but there is no warning information in the next regression. If only the warning information table generated each time is marked, there may be a case where the check is repeated. Based on the research, the method in the embodiment of the application realizes the anti-mark of the warning information by marking the code which correspondingly outputs the warning information in the verification environment based on the correctness of the warning information, so that the warning information can be effectively identified as the checked warning information when the same warning information can be output again. In this way, the check state is recorded directly in the table for recording the checked items, and the warning information list can be reduced gradually, so that the complete check result can be finally realized.

EXAMPLE III

Based on the same application concept, a warning information checking device corresponding to the warning information checking method is further provided in the embodiments of the present application, and since the principle of solving the problem of the device in the embodiments of the present application is similar to that in the embodiments of the warning information checking method, the implementation of the device in the embodiments of the present application may refer to the description in the embodiments of the method, and repeated parts are not described again.

Please refer to fig. 4, which is a schematic diagram illustrating functional modules of an apparatus for checking warning information according to an embodiment of the present disclosure. Each module in the warning information checking apparatus in this embodiment is configured to perform each step in the above-described method embodiment. The warning information checking device comprises a simulation log acquisition module 301, a warning information extraction module 302, a warning information comparison module 303, a first list updating module 304 and a second list updating module 305; wherein, the first and the second end of the pipe are connected with each other,

a simulation log obtaining module 301, configured to simulate a target chip design in a current verification environment to obtain a simulation log file;

a warning information extraction module 302, configured to traverse the simulation log file to extract target warning information in the simulation log file;

a warning information comparison module 303, configured to compare the target warning information with a current warning information list;

a first list updating module 304, configured to, when there is no warning information corresponding to the target warning information in the warning information list, write the target warning information into the warning information list to update the warning information list;

a second list updating module 305, configured to, when warning information corresponding to the target warning information exists in the warning information list and the target warning information carries a set identifier, add a verification identifier to the corresponding warning information in the warning information list to update the warning information list.

In a possible implementation manner, the warning information inspection apparatus provided in an embodiment of the present application may further include: and a verification environment updating module 306, configured to update, according to the warning information in the current warning information list, the warning output field in the current verification environment by using the set identifier when the warning information exists in the warning information list, so as to obtain the current verification environment.

In this embodiment, the execution modules 301 to 305 are repeatedly called to update the warning information list until all the warning information in the warning information list has the verification identifier.

In a possible embodiment, the warning information comparing module 303 is configured to:

In a possible embodiment, each warning message includes a defined field; a warning information comparison module 303, configured to:

when the warning information which is the same as the fields of the target warning information except the limited fields exists in the warning information list, the warning information which corresponds to the target warning information exists in the warning information list.

In a possible implementation manner, each piece of warning information includes multiple pieces of information, each piece of information includes a warning entity and path information, and the defined field is a first field of the warning entity, or the defined field is a second field of the path information.

In a possible implementation manner, each piece of warning information includes multiple pieces of information, the multiple pieces of information include path information, and the path information includes a second field; a warning information comparison module 303, configured to:

comparing fields of the path information in the target warning information except the second field with fields of various items of warning information in the warning information list except the second field;

and when the warning information list has the warning information which is the same as the fields of the target warning information except the second field, representing that the warning information corresponding to the target warning information exists in the warning information list.

In one possible implementation, the verification environment update module 306 is configured to:

In a possible implementation, the first list updating module 304 is configured to:

and when fourth warning information in the warning information list contains a verification identifier and an output field of the fourth warning information in the current verification environment does not contain the set identifier, updating a first warning information output field in the current verification environment by using the set identifier.

Furthermore, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the warning information checking method described in the above method embodiment.

The computer program product of the warning information checking method provided in the embodiment of the present application includes a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the steps of the warning information checking method described in the above method embodiment, which may be specifically referred to in the above method embodiment, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It should be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A warning information checking method, characterized by comprising:

when the warning information list does not have warning information corresponding to the target warning information, writing the target warning information into the warning information list so as to update the warning information list;

when the warning information list has warning information corresponding to the target warning information and the target warning information carries a set identifier, adding a verification identifier to the corresponding warning information in the warning information list to update the warning information list;

and repeating the steps until all the warning messages in the warning message list have the verification identification.

2. The method of claim 1, wherein comparing the target warning information to a list of warning information comprises:

3. The method of claim 2, wherein the warning message includes a defined field; the comparing the specified field in the target warning information with each item of warning information in the warning information list comprises:

4. The method according to claim 3, wherein each warning message includes a plurality of messages including a warning entity and path information, and the defined field is a first field of the warning entity or a second field of the path information.

5. The method of claim 1, wherein comparing the target warning information to a list of warning information comprises:

6. The method according to any one of claims 1-5, further comprising:

and when the warning information exists in the warning information list, updating the warning output field in the current verification environment by using the set identifier according to the warning information in the current warning information list so as to obtain the current verification environment.

7. The method according to claim 6, wherein the updating the warning output field in the current verification environment according to the warning information in the current warning information list using the set identifier to obtain the current verification environment comprises:

8. The method according to claim 6, wherein the updating the warning output field in the current verification environment according to the warning information in the current warning information list using the set identifier to obtain the current verification environment comprises:

9. The method according to claim 6, wherein the updating the warning output field in the current verification environment according to the warning information in the current warning information list using the set identifier to obtain the current verification environment comprises:

and when fourth warning information in the warning information list contains a verification identifier and an output field of the fourth warning information in the current verification environment does not contain the set identifier, updating the fourth warning information output field in the current verification environment by using the set identifier.

10. The method according to any one of claims 1-5, wherein said writing the target warning information into the warning information list to update the warning information list comprises:

11. An alarm information checking apparatus, characterized by comprising:

and the second list updating module is used for adding a verification identifier to the warning information corresponding to the warning information list to update the warning information list when the warning information corresponding to the target warning information exists in the warning information list and the target warning information carries a set identifier.

12. An electronic device, comprising: a processor, a memory storing machine-readable instructions executable by the processor, the machine-readable instructions when executed by the processor performing the steps of the method of any of claims 1 to 10 when the electronic device is run.

13. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1 to 10.