Data management method and device, electronic equipment and computer readable storage medium

Abstract

Embodiments of the present application disclose a data management method and device, electronic equipment and a computer readable storage medium. The method comprises obtaining an initial coding table, saving the initial coding table as a target format file, and in response to an opening instruction, calling a text editor instruction or a table tool instruction, opening the target format file based on an opening mode corresponding to the opening instruction, so that the use and modification of instructions in the target format file are more convenient. Meanwhile, after the target format file is modified, the modified content is received and the modified target format file is saved, so that the modified content of the instructions in the target format file can be updated in time, the updating efficiency is high, and the use accuracy of the instructions is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a data management method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] During instruction set development, it is usually necessary to establish a large instruction decoding table to facilitate the management and adjustment of instructions in the instruction set.

[0003] There are two common methods for editing decoding tables: one is to embed the decoding table into the code using a text editor; the other is to manage the decoding table using spreadsheet software and then use specific tools to convert the spreadsheet content into code after editing. However, while both methods achieve decoding table management, the ease of use and modification, as well as real-time updates, still need improvement. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a data management method, apparatus, electronic device, and computer-readable storage medium to improve the ease of use and modification of decoding tables and the efficiency of real-time updates.

[0005] In a first aspect, embodiments of the present invention provide a data management method, the method comprising:

[0006] Obtain an initial decoding table, which is used to store instructions and the decoding entries for each instruction;

[0007] Save the initial decoding table as a target format file;

[0008] In response to an open command, the target format file is opened based on the open method corresponding to the open command. The types of open commands include commands to invoke a text editor and commands to invoke a table tool. Each type of open command corresponds to an open method.

[0009] Receive the modified content of the target format file and save the modified target format file.

[0010] Furthermore, the type of the open instruction is determined based on the modified content.

[0011] Furthermore, the type of the opening method instruction is determined based on the following steps:

[0012] In response to a change in a portion of the decoded terms of an instruction in the target format file, the open instruction is determined to be a text editor invocation instruction;

[0013] In response to a change in all or the same decoded item of a single instruction in the target format file, the open instruction is determined to be a table tool invocation instruction.

[0014] Furthermore, the target format file includes row information and column information, wherein the row information is used to represent different instructions, and the column information is used to represent the decoding items corresponding to each instruction.

[0015] Furthermore, saving the initial decoding table as a target format file includes:

[0016] Based on the target plugin preset in the hardware code, the instructions in the initial decoding table are saved to the target format table to generate the target format file.

[0017] Furthermore, the method also includes:

[0018] The instructions in the target format file are converted into compilable code based on reflection technology, so as to execute the instructions in the target format file.

[0019] Furthermore, the method also includes:

[0020] In response to the detection of modifications to the target format file, or at preset intervals, the version information of the target format file is saved, wherein the version information includes the modification record of the target format file or the saving time.

[0021] Furthermore, the target format file is a comma-separated value format file.

[0022] In a second aspect, embodiments of the present invention provide a data management device, the device comprising:

[0023] An acquisition unit is used to acquire an initial decoding table, wherein the initial decoding table is used to store instructions and the decoding entries of each instruction;

[0024] The storage unit is used to save the initial decoding table as a target format file, and to receive modifications to the target format file and save the modified target format file.

[0025] An open unit is used to open the target format file in response to an open instruction, based on the open mode corresponding to the open instruction. The types of open instructions include commands to invoke a text editor and commands to invoke a table tool, and each type of open instruction corresponds to an open mode.

[0026] Thirdly, embodiments of the present invention provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method as described in any of the preceding claims;

[0027] The processor's hardware code includes a target format plugin, which is used to save the initial decoding table as a target format file.

[0028] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method described in any of the preceding claims.

[0029] The technical solution of this invention obtains an initial decoding table, saves it as a target format file, and opens the target format file based on the opening method corresponding to the opening command, responding to either a text editor command or a table tool command. This makes the use and modification of commands in the target format file more convenient. Furthermore, after modifications are made to the target format file, the changes are received and the modified target format file is saved, ensuring timely updates to the modified commands in the target format file. This high update efficiency improves the accuracy of command usage. Attached Figure Description

[0030] The above and other objects, features and advantages of the present invention will become clearer from the following description of embodiments of the invention with reference to the accompanying drawings, in which:

[0031] Figure 1 This is a flowchart of the data management method according to Embodiment 1 of the present invention;

[0032] Figure 2 This is a schematic diagram of a target format file opened based on a command to invoke a table tool, according to an embodiment of the present invention.

[0033] Figure 3 This is a flowchart of the data management method according to Embodiment 2 of the present invention;

[0034] Figure 4 This is a schematic diagram of the target format file according to an embodiment of the present invention;

[0035] Figure 5 This is a flowchart of the data management method according to Embodiment 3 of the present invention;

[0036] Figure 6 This is a flowchart of the data management device according to Embodiment 4 of the present invention;

[0037] Figure 7 This is a schematic diagram of the data management device according to Embodiment 5 of the present invention;

[0038] Figure 8 This is a schematic diagram of the data management device according to Embodiment Six of the present invention;

[0039] Figure 9 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0040] The present invention is described below based on embodiments, but the invention is not limited to these embodiments. In the detailed description of the invention below, certain specific details are described in detail. Those skilled in the art will fully understand the invention even without these details. To avoid obscuring the essence of the invention, well-known methods, processes, flows, elements, and circuits are not described in detail.

[0041] Furthermore, those skilled in the art should understand that the accompanying drawings provided herein are for illustrative purposes only and are not necessarily drawn to scale.

[0042] Unless the context explicitly requires it, words such as "including" or "contains" in the instruction manual should be interpreted as including rather than exclusive or exhaustive; that is, meaning "including but not limited to".

[0043] In the description of this invention, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0044] With the rise of RISC-V (an open-source instruction set architecture based on the principles of a reduced instruction set architecture), its open instruction set has led many manufacturers to attempt to develop their own processors with special extensions based on its basic instruction set. This inevitably requires decoding all supported instructions (including RISC-V standard instructions and vendor-specific instructions). Consequently, developers often need to manage a decoding table containing a large number of instructions. The decoding table is a file in the processor hardware code that centrally stores the decoded content of all instructions, containing a large number of instructions and their decoded entries. Furthermore, during development, it is frequently necessary to adjust the instructions in the decoding table, including adding or deleting instructions, adding or deleting decoded entries, and modifying the contents of instruction decoded entries.

[0045] When using a text editor to manage a decoder table, it is convenient to operate on individual instructions. However, when the table is very large, it becomes difficult to add, delete, or move the same decoder item corresponding to different instructions.

[0046] When using spreadsheet tools to manage decoding tables, the process is cumbersome because the edited decoding table requires specific tools to convert the instructions into executable code. This conversion involves first converting the instructions into intermediate code, and then converting the intermediate code into executable code. Furthermore, since both the content in the decoding table and the intermediate code are visible and editable, it's difficult to track instruction modifications, leading to poor consistency and potential errors. For example, updating only the intermediate code without simultaneously updating the spreadsheet, or modifying only the spreadsheet without simultaneously modifying the intermediate code, will disrupt instruction consistency, causing conflicts and overwriting issues between different developers. In severe cases, it can lead to inaccurate instruction execution and project failure.

[0047] In view of this, the embodiments of the present invention aim to provide a data management method to improve the convenience of using and modifying decoding tables, as well as the efficiency of real-time updates. It should be understood that the data management method in this embodiment can be applied to various situations requiring large-scale management of decoding tables.

[0048] Figure 1 This is a flowchart of the data management method according to Embodiment 1 of the present invention. Figure 1 As shown, the data management method in this embodiment includes the following steps.

[0049] In step S110, an initial decoding table is obtained. This initial decoding table stores instructions and their decoding entries.

[0050] In this embodiment, each instruction corresponds to at least one decoding item. Different decoding items can reflect different attributes of the instruction, including whether the corresponding instruction data is valid, whether it is a floating-point type, whether it is a single-precision type, microcode encoding, transmit queue, and execution unit, etc.

[0051] Optionally, the initial decoding table in this embodiment can be generated using a text editor or spreadsheet tool. In this embodiment, for ease of management, the instructions in the initial decoding table are often represented in the form of row information and column information. Row information is used to represent the information of a corresponding instruction, and column information is used to represent different decoding items.

[0052] In step S120, the initial decoding table is saved as a target format file.

[0053] Optionally, in this embodiment, the target format is CSV, and the target file is a CSV file. CSV (Comma-Separated Values), also known as character-separated values, is a file format that stores tabular data in plain text. It consists of any number of records, separated by a newline character. Each record consists of different fields, and the separators between fields are other characters or strings, most commonly commas or tabs. Furthermore, CSV files can be opened and edited using both text editors and spreadsheet tools. It should be understood that this embodiment does not limit the target format; any file storage format that can be accurately opened in text or tabular format can be used in this embodiment.

[0054] Optionally, in this embodiment, the instructions in the initial decoding table are saved to the target format table based on the preset target plugin in the hardware code to generate a target format file.

[0055] Furthermore, the target format file in this embodiment includes row information and column information. The row information is used to represent different instructions, and the column information is used to represent the decoding items of each instruction.

[0056] In step S130, in response to the open command, the target format file is opened based on the open method corresponding to the open command. The types of open commands include commands to call a text editor and commands to call a table tool.

[0057] In this embodiment, each type of open instruction corresponds to an open method.

[0058] Optionally, the type of open instruction is determined based on the modifications made to the target format file. The modifications in the target format file refer to the parts of the target format file that need to be modified. For example, this could involve modifying individual decoded entries of a specific instruction, modifying different decoded entries of several instructions, or uniformly modifying several decoded entries of all instructions. In this embodiment, different open methods can be selected to open the target format file depending on the modifications made, facilitating operation.

[0059] Optionally, the type of open instruction in this embodiment is determined based on the following steps:

[0060] In step S131, in response to a change in a portion of the decoded item of the instruction in the target format file, the open instruction is determined to be a text editor invocation instruction.

[0061] In step S132, in response to a change in all or the same decoded item of a single instruction in the target format file, the open instruction is determined to be a table tool call instruction.

[0062] In one example, the target format file can be further opened using a spreadsheet tool. Figure 2 The image shown is a schematic diagram of a target format file opened using a spreadsheet tool, such as... Figure 2 As shown, the target format file opened using a spreadsheet tool includes row and column information. Row information includes different instruction lines, each consisting of all the decoded entries for the corresponding instruction. Each instruction line is distinguished by its corresponding instruction identifier, such as instructions LW, LH, and SW. Column information includes the decoded entries for each instruction. Each decoded entry characterizes various attributes of the instruction, including whether the instruction data is valid, whether it is a floating-point type, whether it is a single-precision type, microcode encoding, issue queue, and execution unit.

[0063] It should be understood that steps S131 and S132 in this embodiment are parallel. Step S131 is executed when some decoded items of the instructions in the target format file change. Step S132 is executed when all decoded items of a single instruction or the same decoded item of all instructions in the target format file change.

[0064] In this embodiment, optionally, upon receiving an instruction to open the target format file using a text editor, the text editor is invoked to open the target format file. Alternatively, upon receiving an instruction to open the target format file using a table tool, the table tool is invoked to open the target format file.

[0065] In other alternative implementations, the open instruction includes modified content or an identifier corresponding to the modified content, which can be used to indicate that the open instruction is a text editor instruction or a table tool instruction.

[0066] Optionally, upon receiving a request to open a target file, the server may prompt the user to input modifications or select an identifier corresponding to the modifications via a predetermined location or pop-up window. The server then receives the user's modifications or the corresponding identifier to determine whether the open instruction is to invoke a text editor or a spreadsheet tool. It should be understood that other methods, such as opening the target format file using a corresponding opening method based on the modifications or identifier after receiving the modifications, can also be applied to this embodiment, and this embodiment does not limit this approach.

[0067] In step S140, the modified content for the target format file is received, and the modified target format file is saved.

[0068] Optionally, to facilitate viewing the modification history of the target format file, the modification history includes version information such as the content of each modification and the modification time. The data management method in this embodiment further includes:

[0069] In response to the detection of modifications to the target format file, or at preset intervals, version information of the target format file is saved. This version information includes the modification history or save time of the target format file. Each modified version of the target format file, or each automatically saved version at regular intervals, constitutes a version of the file. Version information for each version is stored, and the content of each version of the target format file may be different or the same.

[0070] Optionally, in this embodiment, version control software is used to save the version of the target format file. Furthermore, version tracking software such as Git or SVN, especially text-based code development tools, can be used to manage the version information of the target format file. Therefore, by recording the version information of the target format file, it is convenient to view and understand the modification history of the target format file, further facilitating the management and use of instructions within the target format file.

[0071] The technical solution of this invention obtains an initial decoding table, saves it as a target format file, and opens the target format file based on the opening method corresponding to the opening command, responding to either a text editor command or a table tool command. This makes the use and modification of commands in the target format file more convenient. Furthermore, after modifications are made to the target format file, the changes are received and the modified target format file is saved, ensuring timely updates to the modified commands in the target format file. This high update efficiency improves the accuracy of command usage.

[0072] Figure 3 This is a flowchart of the data management method according to Embodiment 2 of the present invention. Figure 3 As shown, the data management method in this embodiment includes the following steps:

[0073] In step S210, an initial decoding table is obtained. This initial decoding table stores instructions and their decoding entries.

[0074] In this embodiment, the initial decoding table is generated using a text editor or spreadsheet tool.

[0075] In step S220, the initial decoding table is saved as a target format file.

[0076] In this embodiment, the instructions in the initial decoding table are saved to the target format table by a preset target plugin in the processor hardware code to generate a target format file.

[0077] Furthermore, such as Figure 4 As shown in the diagram, the target format in this embodiment is CSV, and the target plugin is a CSV plugin. Specifically, the developer embeds the CSV plugin into the processor hardware code, enabling the initial decoding table to be saved as a CSV file. The re-saved CSV file includes row and column information. The row information represents different instructions, and the column information represents the corresponding decoding item for each instruction. Because CSV files can be opened and edited using text editors and spreadsheet tools (Excel, LibreCalc, etc.), the flexibility of using and modifying instructions in the initial decoding table is enhanced, and the operability is improved.

[0078] In step S230, the instructions in the target format file are converted to execute the instructions in the target format file.

[0079] In this embodiment, reflection technology is used to convert the instructions in the target format file into compilable code for execution. Furthermore, in this embodiment, the developer adds code transformation capabilities to the processor's hardware code by using reflection technology in Chisel or Scala. Scala is a modern programming language that runs on the JVM. Chisel is a new hardware design tool that utilizes some useful features of the Scala language.

[0080] Therefore, this embodiment, through the aforementioned code conversion function, enables the saved target format file to obtain the original code information corresponding to each instruction without requiring additional tools, and dynamically converts the instructions in the target format file into compilable code (i.e., runnable code). This dynamic conversion avoids the use of intermediate code when managing decoding tables using spreadsheet tools in existing technologies, reducing the instruction usage process. Simultaneously, the dynamic conversion process avoids inconsistencies between instruction modifications and intermediate code modifications, ensuring the accuracy of instruction execution.

[0081] The technical solution of this embodiment obtains an initial decoding table and saves it as a target format file. This allows the corresponding instructions in the initial decoding table to be opened and edited using text editors and spreadsheet tools, enhancing the flexibility and operability of using and modifying the instructions in the initial decoding table. Simultaneously, by converting the instructions in the target format file, the instructions in the target format file can be dynamically converted into compilable code. Compared to existing technologies, this avoids the use of intermediate code, reduces the instruction usage process, and also avoids inconsistencies between instruction modifications and intermediate code modifications, ensuring the accuracy of instruction execution.

[0082] Figure 5 This is a flowchart of the data management method according to Embodiment 3 of the present invention. Figure 5 As shown, the data management method in this embodiment includes the following steps:

[0083] In step S310, an initial decoding table is obtained. This initial decoding table stores instructions and their decoding entries.

[0084] In this embodiment, the initial decoding table stores a large number of instructions. The instructions in the initial decoding table include row information and column information. The row information is used to represent the information of a corresponding instruction, and the column information is used to represent different decoding items. Among them, an instruction corresponds to at least one decoding item. Different decoding items can reflect different attributes of the instruction, including whether the corresponding instruction data is valid, whether it is a floating-point type, whether it is a single-precision type, microcode encoding, issue queue, and execution unit, etc.

[0085] In step S320, the initial decoding table is saved as a target format file.

[0086] In this embodiment, the target format is CSV, and the target format file is a CSV file. The developer embeds a CSV plugin into the processor hardware code, enabling the initial decoding table to be saved as a CSV file. The target format file includes row and column information. Row information represents different instructions, and column information represents the corresponding decoding items for each instruction. Because CSV files can be opened and edited using text editors and spreadsheet tools, the flexibility and operability of instructions in the initial decoding table are enhanced.

[0087] Further, when the instructions in the target format file need to be modified, step S330 is executed. When the instructions in the target format file do not need to be modified and can be used directly, step S360 is executed.

[0088] In step S330, in response to the open command, the target format file is opened based on the open method corresponding to the open command. The types of open commands include commands to call a text editor and commands to call a table tool.

[0089] In this embodiment, each type of open instruction corresponds to an open method, and the type of open instruction is determined based on the modifications made to the target format file. The modifications in the target format file refer to the parts of the target format file that need to be modified. For example, this could involve modifying individual decoded entries of a specific instruction in the target format file, modifying different decoded entries of several instructions in the target format file, or uniformly modifying several decoded entries of all instructions in the target format file. In this embodiment, if different modifications are made to the target format file, different open methods can be selected to open the target format file for easier operation.

[0090] Specifically, in response to a change in some decoded items of an instruction in the target format file, the open instruction is determined to be a text editor instruction. In response to a change in all decoded items of a single instruction or the same decoded item of all instructions in the target format file, the open instruction is determined to be a table tool instruction.

[0091] In other words, when it's necessary to add or remove decoded items (column information) or add or remove a specific instruction in a target format file, to save modification time, developers only need to select "spreadsheet" as the opening method for the target format file. This generates an open instruction to invoke a spreadsheet tool, and the processor opens the target format file according to the corresponding open method, locating the corresponding position for the developer to make the preset modifications. Similarly, when it's necessary to modify part of the decoded items in a specific instruction within the target format file, developers only need to select "text editor" as the opening method. This generates a text editor-invoking instruction, and the processor opens the target format file according to the corresponding open method, locating the corresponding position for the developer to make the preset modifications.

[0092] In step S340, the modified content for the target format file is received, and the modified target format file is saved.

[0093] In step S350, in response to the detection of modifications to the target format file, or at preset intervals, version information of the target format file is saved. The version information includes the modification history or save time of the target format file. Each modified version of the target format file, or each automatically saved version at regular intervals, constitutes a version of the file. Version information for each version is stored, and the content of each version of the target format file may be different or the same.

[0094] In this embodiment, version control software such as Git and SVN, especially text code development tools, are used as version control software to manage the version information of the target format file. This makes it easier to view and understand the modification history of the target format file, thereby further facilitating the management and use of the instructions in the target format file.

[0095] In step S360, the instructions in the target format file are converted to execute the instructions in the target format file.

[0096] In this embodiment, the instructions in the target format file are converted into compilable code based on reflection technology in order to execute the instructions in the target format file.

[0097] Furthermore, in this embodiment, the developer uses reflection technology in Chisel or Scala to add code conversion functionality to the hardware code in the processor. This code conversion function allows the instructions in the saved target format file to be dynamically converted into compileable code (i.e., runnable code) without requiring additional tools. Therefore, this dynamic conversion avoids the use of intermediate code when managing decoding tables using spreadsheet tools in existing technologies, reducing the instruction usage process. Simultaneously, the dynamic conversion process avoids inconsistencies between instruction modifications and intermediate code modifications, ensuring the accuracy of instruction execution.

[0098] The technical solution of this embodiment obtains an initial decoding table and saves it as a target format file. This allows the corresponding instructions in the initial decoding table to be opened and edited using text editors and spreadsheet tools, enhancing the flexibility and operability of using and modifying the instructions in the initial decoding table. Simultaneously, by responding to the open command as a text editor call or a spreadsheet tool call command, the target format file is opened based on the opening method corresponding to the open command, making the use and modification of instructions in the target format file more convenient. After the target format file is modified, the modified content is received and the modified target format file is saved, ensuring timely updates of the modified instructions in the target format file, resulting in high update efficiency and improved accuracy of instruction usage. Furthermore, by converting the instructions in the target format file, the instructions in the target format file can be dynamically converted into compilable code. Compared to existing technologies, this avoids the use of intermediate code, reduces the instruction usage process, and prevents inconsistencies between instruction modifications and intermediate code modifications, ensuring the accuracy of instruction execution.

[0099] Figure 6 This is a schematic diagram of the data management device according to Embodiment 4 of the present invention. Figure 6As shown, the data management device in this embodiment includes an acquisition unit 1, a storage unit 2, and an opening unit 3. The acquisition unit 1 acquires an initial decoding table, which stores instructions and their decoding entries. The storage unit 2 saves the initial decoding table as a target format file and receives modifications to the target format file, saving the modified target format file. The opening unit 3 opens the target format file in response to an opening command, based on the opening method corresponding to the command. The types of opening commands include commands to invoke a text editor and commands to invoke a table tool; each type of opening command corresponds to a specific opening method.

[0100] Specifically, the saving unit 2 is used to save the instructions in the initial decoding table to a target format table based on the preset target plugin in the hardware code, so as to generate a target format file. The opening unit 3 is used to determine that the opening instruction is a text editor call instruction in response to a partial change in the decoding items of the instructions in the target format file, and to determine that the opening instruction is a table tool call instruction in response to a change in all decoding items of a single instruction or the same decoding item of all instructions in the target format file.

[0101] Figure 7 This is a schematic diagram of the data management device according to Embodiment 5 of the present invention. Figure 7 As shown, the data management device in this embodiment includes an acquisition unit 1, a storage unit 2, and a conversion unit 4. The acquisition unit 1 acquires an initial decoding table, which stores instructions and their decoding entries. The storage unit 2 saves the initial decoding table as a target format file. The conversion unit 4 converts the instructions in the target format file to execute them. Specifically, the storage unit 2 saves the instructions in the initial decoding table to a target format table based on a preset target plugin in the hardware code, generating a target format file. The conversion unit 4 also converts the instructions in the target format file into compilable code using reflection technology to execute them.

[0102] Figure 8 This is a schematic diagram of the data management device according to Embodiment Six of the present invention. Figure 8As shown, the data management device in this embodiment includes an acquisition unit 1, a storage unit 2, an opening unit 3, a conversion unit 4, and a recording unit 5. The acquisition unit 1 acquires an initial decoding table, which stores instructions and their decoding entries. The storage unit 2 saves the initial decoding table as a target format file and receives modifications to the target format file, saving the modified target format file. The opening unit 3 opens the target format file in response to an opening command, based on the opening method corresponding to the command. Opening commands include commands to invoke a text editor and commands to invoke a table tool; each type of opening command corresponds to a specific opening method. The conversion unit 4 converts the instructions in the target format file to execute them. The recording unit 5 saves version information of the target format file in response to detected modifications or at preset intervals. This version information includes the modification record or the save time of the target format file.

[0103] Specifically, the saving unit 2 is used to save the instructions in the initial decoded table to a target format table based on the preset target plugin in the hardware code, thereby generating a target format file. The opening unit 3 is used to determine that the opening instruction is a text editor call instruction in response to a change in some decoded items of the instructions in the target format file, and to determine that the opening instruction is a table tool call instruction in response to a change in all decoded items of a single instruction or the same decoded item of all instructions in the target format file. The conversion unit 4 is also used to convert the instructions in the target format file into compilable code based on reflection technology, so as to execute the instructions in the target format file.

[0104] The technical solution of this embodiment acquires an initial decoding table through an acquisition unit and saves the initial decoding table as a target format file through a saving unit. This allows the corresponding instructions in the initial decoding table to be opened and edited using text editors and spreadsheet tools, enhancing the flexibility and operability of the instructions in the initial decoding table. Simultaneously, the opening unit responds to the opening command by calling a text editor or a spreadsheet tool, opening the target format file based on the opening method corresponding to the opening command, making the use and modification of instructions in the target format file more convenient. After the target format file is modified, the saving unit receives the modified content and saves the modified target format file, ensuring timely updates of the modified instructions in the target format file, resulting in high update efficiency and improved accuracy of instruction usage. Furthermore, the conversion unit converts the instructions in the target format file, enabling them to be dynamically converted into compilable code. Compared to existing technologies, this avoids the use of intermediate code, reduces the instruction usage process, and prevents inconsistencies between instruction modifications and intermediate code modifications, ensuring the accuracy of instruction execution.

[0105] Figure 9 This is a schematic diagram of an electronic device according to an embodiment of the present invention. (For example...) Figure 9 As shown, Figure 9 The illustrated electronic device 9 is a general-purpose data processing device, comprising a general-purpose computer hardware architecture, including at least a processor 91 and a memory 92. The processor 91 and memory 92 are connected via a bus 93. The memory 92 is adapted to store instructions or programs executable by the processor 91. The processor 91 can be a standalone microprocessor or a collection of one or more microprocessors. Thus, the processor 91 executes the instructions stored in the memory 92, thereby performing the method flow of the embodiments of the present invention as described above to process data and control other devices. Further, the hardware code of the processor 91 in this embodiment embeds a target format plugin, which is used to save the initial decoding table as a target format file. The bus 93 connects the aforementioned components together, and also connects these components to a display controller 94, a display device, and an input / output (I / O) device 95. The input / output (I / O) device 95 can be a mouse, keyboard, modem, network interface, touch input device, motion-sensing input device, printer, and other devices known in the art. Typically, the input / output device 95 is connected to the system via the input / output (I / O) controller 96.

[0106] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus (devices), or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0107] This application is described with reference to flowchart illustrations of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each step in the flowchart can be implemented by computer program instructions.

[0108] These computer program instructions may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction means, the implementation process of which is described in the instruction means. Figure 1 The function specified in one or more processes.

[0109] These computer program instructions may also be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, produce instructions for implementing processes. Figure 1 A device for a function specified in one or more processes.

[0110] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program for use by a computer to execute some or all of the above-described method embodiments.

[0111] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program specifying the relevant hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0112] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. For those skilled in the art, the present invention can be modified and varied in various ways. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data management method, characterized in that, The method includes: Obtain an initial decoding table, which is used to store instructions and the decoding entries for each instruction; Save the initial decoding table as a target format file; the target format file is a comma-separated value format file; the target format file includes row information and column information, the row information is used to represent different instructions, and the column information is used to represent the decoding items corresponding to each instruction; the instructions are RISC-V standard instructions or instructions proprietary to various manufacturers. In response to an open command, the target format file is opened based on the open method corresponding to the open command. The types of open commands include commands to invoke a text editor and commands to invoke a table tool. Each type of open command corresponds to one open method. The type of open command is determined according to the modified content in the target format file. Receive the modified content of the target format file and save the modified target format file; Convert the instructions in the target format file to execute the instructions in the target format file; Saving the initial decoding table as a target format file includes: saving the instructions in the initial decoding table to a target format table based on a preset target plugin in the hardware code, so as to generate the target format file; The step of converting the instructions in the target format file to execute the instructions in the target format file includes: converting the instructions in the target format file into compilable code based on reflection technology to execute the instructions in the target format file; The method further includes: in response to monitoring a modification of the target format file, or at a preset time interval, saving version information of the target format file, wherein the version information includes modification records or saving time of the target format file.

2. The method according to claim 1, characterized in that, The type of the open instruction is determined based on the following steps: In response to a change in a portion of the decoded terms of an instruction in the target format file, the open instruction is determined to be a text editor invocation instruction; In response to a change in all or the same decoded item of a single instruction in the target format file, the open instruction is determined to be a table tool invocation instruction.

3. A data management device, characterized in that, The device includes: An acquisition unit is used to acquire an initial decoding table, wherein the initial decoding table is used to store instructions and the decoding entries of each instruction; A storage unit is used to save the initial decoding table as a target format file, and to receive modifications to the target format file and save the modified target format file; the target format file is a comma-separated value format file; the target format file includes row information and column information, the row information is used to represent different instructions, and the column information is used to represent the decoding items corresponding to each instruction; the instructions are RISC-V standard instructions or instructions proprietary to various manufacturers; An opening unit is used to open the target format file in response to an opening command, based on the opening method corresponding to the opening command. The types of opening commands include commands to invoke a text editor and commands to invoke a table tool, and each type of opening command corresponds to an opening method. The type of the opening command is determined according to the modified content in the target format file. The device further includes: The conversion unit is used to convert the instructions in the target format file in order to execute the instructions in the target format file; The storage unit is also used to save the instructions in the initial decoding table to the target format table based on the target plugin preset in the hardware code, so as to generate the target format file; The conversion unit is also used to convert the instructions in the target format file into compilable code based on reflection technology, so as to execute the instructions in the target format file; The device further includes a recording unit; the recording unit is used to save version information of the target format file in response to monitoring a modification of the target format file, or at preset intervals, wherein the version information includes modification records or saving times of the target format file.

4. An electronic device, comprising a memory and a processor, characterized in that, The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method of any one of claims 1-2; The processor's hardware code includes a target format plugin, which is used to save the initial decoding table as a target format file.

5. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method steps of any one of claims 1-2.

Images