CN112597756B

CN112597756B - Method, device, equipment and storage medium for generating operation statement report

Info

Publication number: CN112597756B
Application number: CN202011495201.5A
Authority: CN
Inventors: 沈旭; 王芳
Original assignee: Haiguang Information Technology Co Ltd
Current assignee: Haiguang Information Technology Co Ltd
Priority date: 2020-12-17
Filing date: 2020-12-17
Publication date: 2022-11-11
Anticipated expiration: 2040-12-17
Also published as: CN112597756A

Abstract

The disclosure provides a method, a device, equipment and a storage medium for generating an operation statement report. The generation method of the operation statement report comprises the following steps: an ignoring rule determining step of analyzing an ignoring rule file and extracting effective ignoring rules; an operation statement processing step, namely analyzing the initial operation statement report according to the neglecting rule to create a corresponding hash array; and multiplexing, namely generating a final operation statement report according to the hash array. The method and the device can realize real-time and reusability of the operation statements in different environments and different stages.

Description

Method, device, equipment and storage medium for generating operation statement report

Technical Field

The present disclosure relates to the field of verification technologies of integrated circuits, and in particular, to a method, an apparatus, a device, and a storage medium for generating an operation statement report.

Background

The functions of the current SOC design are more and more, the scale of the current SOC design is larger and larger, and the verification environment and the verification task corresponding to the SOC design are more and more complex. During project development, some specially-excited operation statements such as force/release/dispose often exist in the verification environment, for example, to simulate power supply connection, to accelerate initialization in simulation, to simulate metastability propagation, to switch checker, and some temporary strain methods to quickly reach some verification targets. The normal verification platform gives the design incentive to meet the functional and timing requirements of a protocol. The operation statement of force/release/position, which is independent of the organized purposeful activity of the verification component, needs extra attention. In particular, the force operation statement, because its definition determines that its impact is higher than the normal drive of the verification platform on the designed circuit, can be serious in consequence once such an operation is erroneous. Therefore, at the project ending stage, all the operation sentences such as force/release/position existing in the verification environment need to be reviewed, and it is ensured that the operation sentences are necessary and correct. With the increasingly large design scale and the increasingly complex verification environment, operation statements such as force/release/dispose may exist in the whole verification environment in large quantities, and how to efficiently check all the special stimuli becomes a key for ensuring the verification quality. For simplicity, the operation statements such as Force/release/dispose will be collectively referred to as Force hereinafter.

The prior art scheme is to search the original code through grep command, and then to review the code line by line through manpower, which has the following problems:

1. there is no guarantee that Force under all conditions is found

a) There are some Force definitions in a function or task, grep can only search for the function or task, and cannot find the original code that really calls the function or task.

b) In addition to the Force from the standard syntax (such as System Verilog), there are also forces from VPI/ACC/UCLI external to the simulation tool that are most likely not found by grep.

2. Not all grep's out Force results are true Force operations. Typically, the Force in the platform script or the Force keyword appearing in the annotation needs to be manually removed, and the method is time-consuming and easy to make mistakes.

3. The reusability is poor, and the mode, process and result of the examination and reading can not be reused in different environments and different stages of the project.

Disclosure of Invention

The present disclosure has been made to solve the above problems, and an object of the present disclosure is to provide a method, an apparatus, a device, and a storage medium for generating a real-time reusable operation statement report in different environments and at different stages.

This disclosure provides this summary in order to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

In order to solve the above technical problem, an embodiment of the present disclosure further provides a method for generating an operation statement report, including,

an ignoring rule determining step of analyzing an ignoring rule file and extracting effective ignoring rules;

an operation statement processing step, namely analyzing the initial operation statement report according to the neglecting rule to create a corresponding hash array;

multiplexing, namely generating a final operation statement report according to the hash array;

wherein the ignore rule comprises at least one of type information or applicable environment information.

In order to solve the above technical problem, an embodiment of the present disclosure further provides an apparatus for generating an operation statement report, including,

the ignoring rule determining module analyzes the ignoring rule file and extracts an effective ignoring rule;

the operation statement processing module analyzes the initial operation statement report according to the neglecting rule to create a corresponding hash array;

the multiplexing module generates a final operation statement report according to the hash array;

In order to solve the above technical problem, an embodiment of the present disclosure further provides a computer device, which adopts the following technical solution, including:

a memory in which a computer program is stored, and a processor which, when executing the computer program, implements the method as described in the foregoing.

In order to solve the above technical problem, an embodiment of the present disclosure further provides a computer-readable storage medium, which adopts the following technical solution, including:

the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method as described above.

According to the technical scheme disclosed by the disclosure, compared with the prior art, the method and the device can realize real-time and reusable operation statement analysis in different environments and different stages, thereby greatly improving the efficiency and ensuring the quality of the verification environment.

Drawings

FIG. 1 is a flow diagram of one embodiment of a method of generating an operational statement report, according to the present disclosure;

FIG. 2 is a schematic diagram of one embodiment of an apparatus to generate operational statement reports, according to the present disclosure;

FIG. 3 is a schematic block diagram of one embodiment of a computer device according to the present disclosure.

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale.

Detailed Description

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure; the terms "including" and "having," and any variations thereof in the description and claims of this disclosure and the description of the above-described figures, are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of the present disclosure or in the foregoing drawings are used for distinguishing between different objects and not for describing a particular order.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the disclosure. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

In order to make the technical solutions of the present disclosure better understood by those skilled in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

First, relevant definitions and terms of one embodiment of the present disclosure are explained.

Regarding initial operation statement report (Force report):

one or more embodiments of the present disclosure provide a method for analyzing and summarizing real-time and reusable operation statements, such as Force statements, based on VCS, and generating a final operation statement report.

The VCS is a front-end simulation tool provided by Synopsys that provides the functionality to generate an initial Force report. A Force report is generated corresponding to each simulation process, and the Force report contains information of each Force in the whole simulation process, and the data volume is huge. For example, for a typical IP verification environment with 1000 cases, the Force report from a simplest test case VCS has the order of hundreds of thousands of lines, and considering again that the Force reports for 1000 different cases may be different, and it is impractical to analyze manually.

The Force report generated by the VCS is divided into two parts, the first part is a Header Section, which lists all the forces in the original code (which are not necessarily executed), and the format is as follows:

ID	Target	Module	File	Line
					…	…	…	…	…

ID: the unique identifier corresponding to the current Force target node;

target: a path from the top layer corresponding to a target node of a required Force;

module: a block where a code corresponding to execution of the Force operation is located;

file: a file where a code for executing the Force operation is located;

line: corresponding to the file line number where the code executing the Force operation is located.

The second part is an Event List Section, which contains all executed forces at each time point in the whole simulation process, and has the following format:

time: the current simulation time xxx has a Force occurrence;

ID: there may be one or more of the Force executed at the current point in time;

TYPE: indicating the type of Force performed for this ID, can be classified as LF, LR, LD, EF, ER, ED:

wherein LF represents a Language Force;

wherein LR represents Language Release;

wherein LD represents Language Deposit/Write;

wherein EF represents External Force;

wherein ER represents External Release;

wherein ED represents External Deposit;

note that: the Force statements can be divided into a Language Force (a standard Language supported by VCS, such as System Verilog) and an External Force (from VPI/ACC/UCLI), a Module/File/Line in a Header Section, and a VALUE in an Event List Section, which exist only in TYPE LF, LD, EF, and ED.

It can be seen from the above definition only that the initial operation statement report of the VCS is long and complex, and the readability is poor. In addition, the report quantity is very large, and the report quantity is scattered in the output report of each use case, so that the manual examination difficulty is very large.

Regarding the ignore rule file (driver file):

the present disclosure provides a custom driver file to ignore Force statements that are really needed. For example, a plurality of environments are designed corresponding to a certain design, some Force statements are shared by all the environments, some are shared by a plurality of environments, and some are specific to each environment, so that the following driver files are defined to realize multiplexing.

<env_1,…,env_n,waiver_id>

Driver rule 1

…

<env_1,…,env_n,waiver_id>

Driver rule m

Wherein each item in the parenthesis is separated by commas, the last item driver _ id represents the type of driver, the front part env represents the applicable environment, common if valid for all environments, comma-separated lists the environments if valid for several environments, and only lists the corresponding environments if valid for only one specific environment, as shown in the following table:

the driver _ id represents the type of driver rule, and can be subdivided into the following categories, as shown in the following table:

wherein, driver _ group _1 is generally applied to the third party VIP or model, and is ignored in whole in units of files, and the rule supports regular matching for the convenience of users.

Driver _ group _2 is generally applied to underlying modules which are instantiated in large numbers or to the forms of certain specific codes, and in order to avoid accidentally omitting additional forms, rules of this type do not support regular matching, that is, only codes which are completely consistent are ignored.

The driver _ group _3 is generally applied to the widely applicable Force to the environment, the Force code can be quickly positioned through the file-module-target, and the later-stage examination and reading of the project are facilitated. Furthermore, to improve efficiency, these rules support regular matching.

Waiver _ group _4 is generally applied to the control of the checker switch in a specific test case, and the usage of the checker switch is similar to the use of Waiver _ group _3, but a new scope is added: the use case is tested so that it is only ignored for this use case.

[ method of generating report of operation statement ]

Referring to FIG. 1, a flow diagram of one embodiment of a method of generating an operational statement report in accordance with the present disclosure is shown. The generation method of the operation statement report comprises the following steps:

an ignore rule determining step S11, parses the ignore rule file, and extracts a valid ignore rule.

In one or more embodiments, the override rule includes at least one of type information or applicable context information.

In one or more embodiments, there may be, for example, a total of 10 verification environments, where the override rules may include, for example:

1. common, group-1> ignore rule applicable to all environments: common, group _1> represents the rule of File type applicable to all environments, such as the third party analog circuit model used in all verification environments, in order to speed up the simulation, there will be a lot of Force, the rules shown in the following table can be used to ignore all files whose IP File names meet third party _ anlg _ model.v, where any character is represented, and is used in the regular expression.

File
	third_party_anlg_.*_model.v

2. The < common, group-2> ignore rule applicable to all contexts: < common, group _2> indicates the rule of the type Module-Waiver _ exp applicable to all environments, as shown in the following table, which is a widely used synchronizer Module cdc _ model in a verification environment, in order to model an unsteady propagation model, the clock signal CK Force is x for a period of time and then released at the initial moment of simulation, so the rules can be ignored by using Waiver _ exp "Force CK =1' bx" and "release CK" shown in the following table.

Module	Waiver-exp
		cdc_model	force CK＝1’bx；
cdc_model	release CK；

3. The < common, group-3> ignore rule applicable to all contexts: < common, group _3> indicates a rule of the File-Module-Target type applicable to all environments, such as the Module reset _ gen defined in the File reset _ gen.v, which will perform a Force on the sub-instantiated unit reset _ gen _ sync.inst1.inst2.inst3.enrand below it to enable randomness, and therefore can be ignored with the rules shown in the following table.

4. The < IP, group-3> ignore rule applicable to IP environment: besides the ignoring rules shared by the environments, there are also unique parts of the IP environment, and the rules shown in the following table indicate that Force from the analog model power supply pins (vp, vph, vpdig, vss0, vss1, vss2, vss 3) in the module top in the top-level file top.

5. The < IP, group-4> ignore rule applicable to IP environment: the rules as shown in the table below indicate that the Force from the IP environment test case reset _ test to the signal top.dut. Force _ check _ off via the module IP _ if in the file IP _ if.sv, which is desired by the user to turn off a particular checker during reset, is ignored.

test	file	module	Target
				reset_test	ip_if.sv	ip_if	top\.dut\.force_check_off

To summarize, listing the more complete rules for ignorance that may be encountered in actual review, the present disclosure removes the write/file/module/case that is identified as ignorable from the ignore file by automatically analyzing and summarizing the rules listed for the ignore file.

In one or more embodiments, the ignoring rule determining step S11 further includes checking type information and/or an applicable environment of the ignoring rule file, and extracting all rules corresponding to the type information and/or the applicable environment if the type information and/or the applicable environment are valid; and judging whether the type information and/or the applicable environment of the neglected rule file are completely checked, if not, continuing checking, and if so, entering the subsequent steps.

In one or more embodiments, the generation method of the operation statement report of the present disclosure further includes an ignore rule storage step of verifying correctness of the ignore rule and storing the extracted valid ignore rule in classification according to the target environment and the rule type.

In one or more embodiments, the method for generating an operation statement report of the present disclosure further includes ignoring the rule definition step, and defining type information and/or applicable environment information in advance.

By neglecting the same file, the multiplexing of the Force analysis of the IP environment and other environments can be realized. The validation personnel may define the relevant rules at the beginning of the project. As the project progresses, the Force confirmed by multiple parties is gradually generalized into different ways of ignoring rules. By using the skip file, the retrieval results of different stages of the project can be recorded to the next stage and even the next project can be reused. Ideally, the convergence of one item Force review is flagged with the output table being null.

An operation statement processing step S12 of analyzing the initial operation statement report according to an ignoring rule to create a corresponding hash array;

in one or more embodiments, the operation sentence processing step S12 includes at least:

a first part analysis step, namely analyzing a header part, namely a first part, of an initial operation statement report, such as a Force report, so as to create a first hash array with a target node identifier of an operation statement as an index; for example, the Header Section is analyzed first, a hash array with the ID as an index is created, the value of the hash array is another two-dimensional hash array, and all information for performing Force on the target node corresponding to the current ID is included.

In one or more embodiments, the first dimension index of the first hash array is a self-increment number starting from 1, and the second dimension index is path information of the operation statement. Because the Force of the same Target node may come from different files or different lines of the same File, a two-dimensional hash array is needed to store the information, the first dimension index of the array is a self-increment sequence number from 1, each index represents a group of Force information of the Target node, and the second dimension index contains more specific information of File, line, module and Target, namely, the path information at least comprises one of the path from the top layer of the Target node, the Module where the operation statement is located, the File where the operation statement is located and the File Line number where the operation statement is located.

In one or more embodiments, the data structure of the first hash array corresponding to one ID Header Section information may be as shown in the following table:

in one or more embodiments, the first part analyzing step further includes reading a header part of the initial operation statement report line by line, judging whether the operation statement conforms to an ignoring rule, and if so, ignoring the operation statement according to the ignoring rule, namely skipping the current Force ID; if not, a first hash array with the target node identification of the operation statement as an index is created, all information corresponding to the ID is extracted and stored in the first hash array, and the step is repeated until all Header Section information is processed; and judging whether all the header parts are checked, and if not, continuing to check.

a second part analyzing step of analyzing an event list part, namely a second part, of the initial operation statement report to resolve a second hash array of the information of the operation statement for the target node; for example, event List Section is analyzed, and specific information of performing Force on a target node (which can be characterized by a unique ID) in a simulation process is analyzed from the Event List Section, wherein the specific information includes time, type and value of each Force occurrence.

In one or more embodiments, the first dimension index of the second hash array is attribute information of the operation statement, the attribute information may include, for example, at least one of an execution time of the operation statement, a type of the operation statement, and an execution value of the operation statement, that is, the first dimension index is a string time, a type, and a value, the second dimension index is a time sequence of an initial operation statement report, for example, the second dimension index is a sequence number of a Force performed according to a simulation precedence sequence, and the value is a time, a type, and a value of the Force corresponding to a time point.

In one or more embodiments, the data structure of the second hash array corresponding to an ID Event List Section information is as follows:

and a combining step, namely combining the first hash array and the second hash array to obtain a combined hash array corresponding to the time sequence of the initial operation statement report, namely combining the information analyzed by the Header Section and the Event List Section, extracting the Force information of each time point, analyzing the information extracted in the first part of analyzing step, storing the information into the combined hash array corresponding to each Force ID shown in the following table, and repeating the step until all the Event List Section information is processed to obtain the specific information corresponding to all the forces in the whole simulation time.

In one or more embodiments, the data structure of the combined hash array corresponding to an ID Force information may be as shown in the following table:

a multiplexing step S13, generating a final operation statement report according to the hash array to realize the multiplexing of the operation statements;

generating a preset file format, such as a Force report of Excel, according to the combined hash array generated in the combining step, wherein the format is as shown in the following table:

in one or more embodiments, the multiplexing step S13 further includes a report simplification step, which generates an intermediate Force report in a preset file format, such as Excel, according to the hash array, removes attribute information in the intermediate report, and generates a final operation statement report.

In one or more embodiments, the forms in the form report are derived from the same file, and different values of the same target node at different time points at the same position are considered to be different, but in practice, the forms of this type are all triggered by the same code, and the user only needs to check once, so that the report is further simplified, the attribute information of time, type and value is removed, a simplified form report shown in the following table is finally generated, and the original form report with poor tedious readability is converted into an Excel table with good readability (ignoring attribute information such as time/type/value):

file	line	module	target
				reset_gen.v	line_1	reset_gen	target_1
top.sv	line_2	top	target_2

taking the simplest test case of the IP environment in the embodiment as an example, the original Force report has a total of 469572 lines, and when the neglect rule applicable to all environments is applied, 725 unique Force IDs and 204 corresponding unique target Force nodes are also provided; after further application of the ignoring rules applicable to the IP environment, 34 unique Force IDs and 4 corresponding unique target Force nodes are also arranged; the neglecting rules are all checked manually, so that the neglecting forces are all correct, the remaining forces need to be checked by a design verifier to confirm the necessity, if indeed the rules need to be updated, the neglecting rules are updated, and finally an empty Force report is obtained, if not, the verification environment needs to be updated, the unnecessary forces are removed, and the verification quality is ensured.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless otherwise indicated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by a computer program, which may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read Only Memory (ROM), or a Random Access Memory (RAM).

[ means for generating report of operation statement ]

As shown in fig. 2, in order to implement the technical solution in the embodiment of the present disclosure, the present disclosure provides a device for generating an operation statement report, which may be specifically applied to various electronic terminal devices.

The apparatus for generating an operation statement report according to this embodiment includes: an ignoring rule determining module 201, an operation statement processing module 202 and a multiplexing module 203.

The ignore rule determining module 201 parses the ignore rule file and extracts the valid ignore rule.

In one or more embodiments, for example, there may be a total of 10 verification environments, wherein the rules for ignoring are the same as those described above, and in summary, the disclosure removes the writing/file/module/case that identifies the ignorance from the ignore file by automatically analyzing and summarizing the rules listed in the ignore file, listing the ignore rules that may be encountered in a relatively complete actual review.

In one or more embodiments, the ignore rule determining module 201 is further configured to check the type information and/or the applicable environment of the ignore rule file, and if the type information and/or the applicable environment are valid, extract all the rules corresponding to the type information and/or the applicable environment; and judging whether the type information and/or the applicable environment of the neglected rule file are completely checked, if not, continuing checking, and if so, entering the subsequent steps.

In one or more embodiments, the generation apparatus of the operation statement report of the present disclosure further includes an ignore rule storage module for verifying correctness of the ignore rule and storing the extracted valid ignore rule in a classification manner according to the target environment and the rule type.

In one or more embodiments, the generation apparatus of an operation statement report of the present disclosure further includes an ignore rule defining module for predefining type information and/or applicable environment information.

By neglecting the same file, the multiplexing of the Force analysis of the IP environment and other environments can be realized. The verifier may define the relevant rules at the beginning of the project. As the project progresses, the Force confirmed by multiple parties is gradually generalized into different ways of ignoring rules. By using the skip file, the retrieval results of different stages of the project can be recorded to the next stage and even the next project can be reused. Ideally, the convergence of one item Force review is flagged with the output table being null.

An operation statement processing module 202, which analyzes the initial operation statement report according to the ignoring rule to create a corresponding hash array;

in one or more embodiments, the operational statement processing module 202 includes at least:

the first part analysis module is used for analyzing a header part, namely a first part, of the initial operation statement Force report to create a first hash array with the target node identification of the operation statement as an index; for example, the Header Section is analyzed first, a hash array with the ID as an index is created, the value of the hash array is another two-dimensional hash array, and all information for performing Force on the target node corresponding to the current ID is included.

In one or more embodiments, the first dimension index of the first hash array is a self-increment number starting from 1, and the second dimension index is path information of the operation statement. Because the Force of the same Target node may come from different files or different lines of the same File, a two-dimensional hash array is needed to store the information, the first-dimensional index of the array is a self-increment sequence number from 1, each index represents a group of Force information of the Target node, and the second-dimensional index contains more specific File, line, module and Target information, i.e. the path information at least comprises one of the path from the top layer of the Target node, the Module where the operation statement is located, the File where the operation statement is located, and the Line number of the File where the operation statement is located.

In one or more embodiments, the data structure of the first hash array corresponding to one ID Header Section information may be as shown in the foregoing table, and is not described again.

In one or more embodiments, the first part analysis module is further configured to read a header part of the initial operation statement report line by line, determine whether the operation statement conforms to an ignore rule, and if so, ignore the operation statement according to the ignore rule, that is, skip the current Force ID; if not, a first hash array with the target node identification of the operation statement as an index is created, all information corresponding to the ID is extracted and stored in the first hash array, and the step is repeated until all Header Section information is processed; and judging whether all the header parts are checked, and if not, continuing to check.

the second part analysis module is used for analyzing the event list part, namely the second part of the initial operation statement report so as to analyze a second hash array of the information of the operation statement aiming at the target node; for example, an Event List Section is analyzed, and specific information of performing Force on a target node (which can be characterized by a unique ID) in a simulation process is analyzed from the Event List Section, wherein the specific information includes time, type and value of each Force occurrence.

In one or more embodiments, the data structure of the second hash array corresponding to one ID Event List Section information is shown in the foregoing table, and is not described again.

In one or more embodiments, the operation statement processing module 202 includes at least:

and the combination module is used for combining the first hash array and the second hash array to obtain a combination hash array corresponding to the time sequence of the initial operation statement report, namely combining the information analyzed by the Header Section and the Event List Section, extracting the Force information of each time point, analyzing the information extracted by the first part of analysis module, storing the information into the combination hash array corresponding to each Force ID shown in the table, and repeating the step until all the Event List Section information is processed to obtain the specific information corresponding to all the forces in the whole simulation time.

In one or more embodiments, the data structure of the combined hash array corresponding to one ID Force information may be as shown in the foregoing table, and is not described again.

The multiplexing module 203 generates a final operation statement report according to the hash array so as to realize the multiplexing of the operation statements;

the preset file format, for example, the Force report of Excel, is generated according to the combined hash array generated in the combining module, and the format is shown in the table, which is not described again.

In one or more embodiments, the multiplexing module 203 further includes a report simplification module, which generates an intermediate Force report in a preset file format, such as Excel, according to the hash array, removes attribute information in the intermediate report, and generates a final operation statement report.

In one or more embodiments, the forms in the form report are derived from the same file, and different values of the same target node at different time points at the same position are considered to be different, but in practice, the forms of the type are triggered by the same code, and a user only needs to check once, so that the report is further simplified, the attribute information of time, type and value is removed, a simplified form report shown in the table is finally generated, and the original form report with complicated and tedious readability is converted into an Excel table with good readability (the attribute information of time/type/value and the like is ignored).

It should be understood that although each block in the block diagrams of the figures may represent a module, a portion of which comprises one or more executable instructions for implementing the specified logical function(s), the blocks are not necessarily executed sequentially. Each module and functional unit in the device embodiments in the present disclosure may be integrated into one processing module, or each unit may exist alone physically, or two or more modules or functional units are integrated into one module. The integrated modules can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer-readable storage medium. The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.

[ Generation device of operation statement report ]

Referring now to fig. 3, a schematic diagram of an electronic device (e.g., a terminal device or server) 300 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiment of the present disclosure may be various terminal devices in the above system. The electronic device shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 3, the electronic device 300 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 301 for controlling the overall operation of the electronic device. The processing device may include one or more processors to execute instructions to perform all or a portion of the steps of the method described above. Further, the processing device 301 may also include one or more modules for processing interactions with other devices.

Storage device 302 is used to store various types of data, and storage device 302 can be a system, apparatus or device that includes various types of computer-readable storage media or a combination thereof, such as electronic, magnetic, optical, electromagnetic, infrared, or semiconductor, or a combination of any of the above. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The sensor means 303, which senses the prescribed measured information and converts it into a usable output signal according to a certain rule, may comprise one or more sensors. For example, it may include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor or a temperature sensor, etc. for detecting changes in the on/off state, relative positioning, acceleration/deceleration, temperature, humidity, light, etc. of the electronic device.

The processing means 301, the storage means 302 and the sensor means 303 are connected to each other by a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.

The multimedia device 306 may include an input device such as a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, etc. for receiving an input signal from a user, and the various input devices may cooperate with various sensors of the sensor device 303 to perform, for example, a gesture operation input, an image recognition input, a distance detection input, etc.; the multimedia device 306 may also include output devices such as a Liquid Crystal Display (LCD), speakers, vibrators, and the like.

The power supply device 307, which is used to provide power to various devices in the electronic equipment, may include a power management system, one or more power supplies, and components to distribute power to other devices.

The communication device 308 may allow the electronic device 300 to communicate with other devices wirelessly or by wire to exchange data.

Each of the above devices may also be connected to the I/O interface 305 to implement applications of the electronic device 300.

While fig. 3 illustrates an electronic device 300 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, the processes described above with reference to the flow diagrams may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means, or may be installed from a storage means. The computer program, when executed by a processing device, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

It is noted that the computer readable medium described above in this disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. In contrast, in the present disclosure, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network or connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. 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 that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Wherein the name of an element does not in some cases constitute a limitation on the element itself.

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.

According to one or more embodiments of the present disclosure, there is provided a method for generating an operation statement report, including:

According to one or more embodiments of the present disclosure, there is provided a method of generating an operation statement report, characterized in that,

the step of determining the ignore rule further comprises,

checking the type information and/or the applicable environment of the ignore rule file,

if the type information and/or the applicable environment are valid, extracting all rules corresponding to the type information and/or the applicable environment;

and judging whether the type information and/or the applicable environment of the ignoring rule file are/is completely checked, and if not, continuing checking.

According to one or more embodiments of the present disclosure, there is provided a method for generating an operation statement report, characterized in that,

the initial operation statement report is a report generated by the VCS, which includes a header portion and an event list portion,

the operation statement processing step at least comprises:

a first part analysis step of analyzing the header part of the initial operation statement report to create a first hash array indexed by a target node identification of the operation statement;

a second part analyzing step of analyzing the event list part of the initial operation statement report to resolve a second hash array of the information of the operation statement for the target node;

and combining the first hash array and the second hash array to obtain a combined hash array corresponding to the time sequence of the initial operation statement report.

the first dimension index of the first hash array is a self-increment sequence number from 1, and the second dimension index is the path information of the operation statement;

and the first dimension index of the second hash array is the attribute information of the operation statement, and the second dimension index is the time sequence reported by the initial operation statement.

the path information at least comprises one of a path from the top layer of the target node, a module where the operation statement is located, a file where the operation statement is located and a file line number where the operation statement is located;

the attribute information at least comprises one of the operation statement execution time, the type of the operation statement and the value executed by the operation statement.

the step of multiplexing further comprises the step of multiplexing,

and a report simplification step, namely generating an intermediate report in a preset file format according to the combined hash array, removing the attribute information in the intermediate report, and generating the final operation statement report.

the first partial analysis step may further comprise,

reading the header portion of the initial operation statement report line by line,

determining whether the operation statement complies with the ignore rule,

if yes, ignoring the operation statement according to the ignoring rule;

if not, a first hash array with the target node identification of the operation statement as an index is created;

and judging whether all the header parts are checked, and if not, continuing to check.

According to one or more embodiments of the present disclosure, there is provided a method for generating an operation statement report, further comprising,

and an ignoring rule storing step, namely verifying the correctness of the ignoring rule and storing the extracted effective ignoring rule in a classified manner according to the target environment and the rule type.

and an ignoring rule defining step of defining the type information and/or the applicable environment information in advance.

According to one or more embodiments of the present disclosure, there is provided an operation statement report generation apparatus, including,

the neglect rule determining module analyzes the neglect rule file and extracts an effective neglect rule;

the operation statement processing module analyzes the initial operation statement report according to the ignoring rule to create a corresponding hash array;

According to one or more embodiments of the present disclosure, there is provided an operation statement report generation apparatus, characterized in that,

the ignore rule determination module is further operable to,

the operation statement processing module at least comprises:

a first part analysis module for analyzing the header part of the initial operation statement report to create a first hash array with the target node identification of the operation statement as an index;

a second part analysis module for analyzing the event list part of the initial operation statement report to resolve a second hash array of the information of the operation statement for the target node;

and the combining module is used for combining the first hash array and the second hash array to obtain a combined hash array corresponding to the time sequence of the initial operation statement report.

the multiplexing module further comprises a multiplexer for multiplexing the received data,

and the report simplification module is used for generating an intermediate report in a preset file format according to the combined hash array, removing the attribute information in the intermediate report and generating the final operation statement report.

the first partial analysis module is further configured to,

determining whether the operation statement complies with the ignore rule,

if yes, ignoring the operation statement according to the ignoring rule;

According to one or more embodiments of the present disclosure, there is provided an operation statement report generation apparatus, further comprising,

and the ignoring rule storage module is used for verifying the correctness of the ignoring rule and storing the extracted effective ignoring rule in a classified mode according to the target environment and the rule type.

and the ignoring rule defining module is used for predefining the type information and/or the applicable environment information.

According to one or more embodiments of the present disclosure, a computer device is provided, which includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method according to any one of the above.

According to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, characterized in that a computer program is stored thereon, which, when being executed by a processor, implements the method of any of the above.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other combinations of features described above or equivalents thereof without departing from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method for generating an operation statement report, comprising,

an operation statement processing step, namely analyzing the initial operation statement report according to the ignoring rule to create a corresponding hash array;

wherein the ignore rule at least comprises one of type information or applicable environment information;

the operation statement processing step at least comprises the following steps:

a first part analysis step of analyzing a header part of the initial operation statement report to create a first hash array indexed by a target node identifier of the operation statement;

2. The generation method of an operation statement report according to claim 1,

the step of determining the ignore rule further comprises,

3. The generation method of an operation statement report according to claim 1,

4. The generation method of an operation statement report according to claim 3,

5. The generation method of an operation statement report according to claim 4, characterized in that,

the step of multiplexing further comprises the step of multiplexing,

6. The generation method of an operation statement report according to claim 1, characterized in that,

the first partial analysis step may further comprise,

determining whether the operation statement complies with the ignore rule,

if yes, ignoring the operation statement according to the ignoring rule;

if not, creating a first hash array with the target node identification of the operation statement as an index;

7. The generation method of an operation statement report according to claim 1, characterized by further comprising,

8. The generation method of an operation statement report according to claim 1, characterized by further comprising,

and a rule definition step of defining the type information and/or the applicable environment information in advance.

9. An apparatus for generating an operation statement report, comprising,

wherein the ignore rule comprises at least one of type information or applicable environment information;

the operation statement processing module at least comprises:

a combining module that combines the first hash array and the second hash array to obtain a combined hash array corresponding to a temporal order of the initial operation statement report.

10. The generation apparatus of an operation statement report according to claim 9,

the ignore rule determination module is further operable to,

11. The generation apparatus of the operation statement report according to claim 9,

12. The generation apparatus of an operation statement report according to claim 11,

13. The generation apparatus of an operation statement report according to claim 12,

14. The generation apparatus of an operation statement report according to claim 9,

the first partial analysis module is further configured to,

determining whether the operation statement complies with the ignore rule,

if yes, ignoring the operation statement according to the ignoring rule;

15. The generation apparatus of an operation statement report according to claim 9, characterized by further comprising,

and the ignoring rule storage module is used for verifying the correctness of the ignoring rule and storing the extracted effective ignoring rule in a classified manner according to the target environment and the rule type.

16. The generation apparatus of an operation statement report according to claim 9, characterized by further comprising,

17. A computer device comprising a memory having stored therein a computer program and a processor implementing the method of any one of claims 1-8 when executing the computer program.

18. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method according to any one of claims 1-8.