KR20170055392A - Method and apparatus for processing graphics command - Google Patents

Abstract

A method for processing a graphics command includes the step of receiving the graphics command from a device executing an application. At least one shader included in the graphics command to be processed by a graphics processor is selected and a shader program is generated by using the at least one shader which is selected. A searched shader program is outputted by searching for a shader program identical to the shader program generated from at least one shader program previously compiled. Accordingly, the present invention can omit an operation by delaying the graphics command.

Description

METHOD AND APPARATUS FOR PROCESSING GRAPHICS COMMAND BACKGROUND OF THE INVENTION [0001]

To a method and apparatus for processing graphics commands.

The Graphics Processing Unit (GPU) can process graphics APIs such as OpenGL ES and OpenCL (CUDA) to realize brilliant graphics effects on mobile devices and TVs.

In order for a program to be processed on the GPU, the program must be written according to the standard rules of the standard API. Programs processed on the GPU consist of a vertex shader and a pixel shader that are essential for image generation. Vertex shaders and pixel shaders are compiled and linked to the program.

With the brilliant graphics effects in applications used in mobile devices and TVs, the program size of applications being processed on the GPU is increasing. As the size of the program processed by the GPU increases, it takes a lot of time to compile and link the vertex shader and the pixel shader that constitute the program. Especially, in the program used in the game, many shaders are repeatedly used to realize the same effect .

And a method and apparatus for processing a graphics command. The present invention also provides a computer-readable recording medium on which a program for causing the computer to execute the method is provided. The technical problem to be solved by this embodiment is not limited to the above-mentioned technical problems, and other technical problems can be deduced from the following embodiments.

CLAIMS What is claimed is: 1. A method of processing a graphics instruction, the method comprising: receiving the graphics instruction from an apparatus executing an application; Selecting at least one shader included in the graphics instruction to be processed in the graphics processor; Generating a shader program using at least one selected shader; Searching for a shader program identical to the generated shader program among at least one previously compiled shader program; And outputting the retrieved shader program.

According to another aspect, there is provided a graphics instruction processing apparatus comprising: a graphics processing unit that receives a graphics command from an apparatus executing an application, selects at least one shader to be processed in a graphics processor included in the graphics command, A processor for generating a shader program using the generated shader program and searching for a shader program identical to the generated shader program among at least one previously compiled shader program and outputting the searched shader program; And a cache that stores previously compiled shader programs.

According to another aspect, there is provided a graphics processing unit (GPU) for receiving a graphics command from an apparatus executing an application, selecting at least one shader to be processed in a graphics processor included in the graphics command, A graphics driver for searching for a same shader program as the generated shader program from among at least one previously compiled shader program and outputting the retrieved shader program; And a cache that stores previously compiled shader programs.

According to another aspect, a computer-readable non-volatile recording medium recording a program for execution on a computer records the method of the first aspect as a program for executing the method on a computer.

According to the above, the computation can be omitted by delaying the graphics command. Also, when the shader program is regenerated, the amount of computation can be reduced by omitting the process of compiling the shader program by reusing the previously stored shader program binaries.

1 is a flow diagram of a method for processing graphics instructions in accordance with one embodiment.
2 is a diagram illustrating an example in which a graphics command is processed in a graphics command processing apparatus located outside a GPU according to an exemplary embodiment.
FIG. 3 is a diagram illustrating an example in which a graphics command is processed in a graphics command processing apparatus located inside a GPU according to an exemplary embodiment of the present invention.
4 is a block diagram of a shader program manager according to an embodiment.
5 is a diagram illustrating an example of searching a shader program in a work processor according to an embodiment.
6 is a diagram illustrating an example in which a graphics instruction processing apparatus according to an embodiment searches for and outputs a shader program.
7 is a diagram specifically illustrating an example of a process of processing data in the graphics instruction processing apparatus according to an embodiment.
8 is a detailed flowchart of a method of processing a graphics command according to an embodiment.
9 is a flowchart of a method of processing a shader program related API by a graphics driver according to an exemplary embodiment.
10 is a flowchart of a method of processing a shader program related API by a shader program manager according to an exemplary embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly describe the present invention in the drawings, parts not related to the description are omitted, and similar parts are denoted by similar reference numerals throughout the specification, and redundant description is omitted.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when a part is referred to as "including " an element, it does not exclude other elements unless specifically stated otherwise.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a flow diagram of a method for processing graphics instructions in accordance with one embodiment. In step 101, when a request to process a graphics command is made in the application, the graphics command processing apparatus receives a graphics command from the apparatus executing the application. A graphics command may include an instruction that can be processed by the GPU. For example, a shader program related API may be included.

In step 102, the graphics instruction processing device may select at least one shader to be processed in the graphics processor, contained in the graphics instruction received in step 101. A shader to be processed by a graphics processor may include a vertex shader and a pixel shader. However, it is not limited thereto.

In step 103, the graphics instruction processing device can generate a shader program using at least one shader selected in step 102. [ A shader program is a unit or type of program that can be processed by a GPU. The shader program may include the uniform data received by the shader and graphics instruction processing device selected in step 102. [ However, it is not limited thereto.

In step 104, the graphics command processing device can search for the same shader program as the shader program generated in step 103 among at least one previously compiled shader program. The graphics command processing device uses the source code (or compiled code), the uniform data, the compiler version, and the GPU version information of the vertex shader and pixel shader included in the shader program to generate the same shader program You can search for programs. The graphics instruction processing device can search for the same shader program as the shader program generated in step 103 using the length of the text and text of the shader source code, the text of the uniform data, and the length of the text. The graphics command processing device can generate the key using the length of the text and text of the shader source code, the text and text length of the uniform data, the compiler version, and the GPU version information. The graphics command processing device can retrieve the same key as the generated key. The key is unique data for identifying the shader program. In other words, different keys are generated for each shader program.

In step 105, the graphics command processing device may output the shader program retrieved in step 104. [ The graphics command processing device can output the searched shader program to a graphics driver or a graphics processor. The shader program manager can output the shader program retrieved in step 104 as a binary.

1 may be stored in a memory in the form of a program or an instruction, and may be implemented by a main processor, a GPU, a shader program manager, a graphics driver, or the like. However, it is not limited thereto.

2 is a diagram illustrating an example in which a graphics command is processed in a graphics command processing apparatus located outside a GPU according to an exemplary embodiment.

Referring to FIG. 2, the graphics instruction processing device may be implemented by the main processor 10 or the shader program manager 100. The shader program manager 100 may be located outside the GPU 20.

The GPU 20 may include a graphics driver 200, a graphics processor 300, and a compiler 500.

The main processor 10 may include a shader program manager 100 and a cache 400.

The cache 400 may store at least one previously compiled shader program. The cache 400 may store the shader program as a binary. The cache 400 may store a key generated using the information included in the shader program 1000a. The key may be generated using the length of the text and text of the shader source code, the length of the text and text of the uniform data, the compiler version, and the GPU version information. However, it is not limited thereto.

The shader program manager 100 may receive a graphics command. The shader program manager 100 may select at least one shader to be processed in the graphics processor included in the received graphics instruction. The shader program manager 100 may generate a shader program using at least one selected shader. The shader program manager 100 can search for the same shader program as the generated shader program among at least one previously compiled shader program and output the retrieved shader program.

The shader program manager 100 can use the key in the step of searching for the same shader program as the generated shader program 1000a. In one embodiment, the shader program manager 100 may generate a key using the information contained in the generated shader program 1000a. In addition, the key generated by the shader program manager 100 may be stored in the cache 400. When the key is stored in the cache, the shader program manager 100 compares the key of the generated shader program 1000a with the key of the shader program stored in the cache 400, thereby obtaining the same shader program as the generated shader program 1000a It can be retrieved from the cache 400.

When the shader program manager 100 searches for the same shader program as the generated shader program 1000a, the shader program manager 100 can output the searched shader program. When the same shader program is searched, the shader program manager 100 can output the searched shader program to the graphics driver 200. [ The shader program manager 100 can output the searched shader program as a binary. The binary is data of a form recognizable by the graphics processor 300.

The shader program manager 100 can output the generated shader program 1000a to the graphics driver 200 when the shader program manager 100 fails to search for the same shader program as the generated shader program 1000a. When the generated shader program 1000a is output to the graphics driver 200, the graphics driver 200 can compile the input shader program 1000a using the compiler 500 to generate a binary. The graphics driver 200 can output the generated binary to the graphics processor 300. [ The graphics driver 200 may store the generated binaries in the cache 400. [ The shader program manager 100 may store the key of the shader program 1000a used for the search in the cache 400. [

FIG. 3 is a diagram illustrating an example in which a graphics command is processed in a graphics command processing apparatus located inside a GPU according to an exemplary embodiment of the present invention.

Referring to FIG. 3, the graphics instruction processing apparatus may be implemented by the graphics driver 200 or the shader program manager 100. However, it is not limited thereto. The shader program manager 100 may be located within the GPU 20.

The GPU 20 may include a graphics driver 200, a graphics processor 300, a cache 400 and a compiler 500.

The cache 400 may store at least one previously compiled shader program. The cache 400 may store the shader program as a binary. The cache 400 may store a key generated using the information included in the shader program 1000a. The key may be generated using the length of the text and text of the shader source code, the length of the text and text of the uniform data, the compiler version, and the GPU version information. However, it is not limited thereto.

The shader program manager 100 may receive a graphics command. The shader program manager 100 may select at least one shader to be processed in the graphics processor included in the received graphics instruction. The shader program manager 100 may generate a shader program using at least one selected shader. The shader program manager 100 can search for the same shader program as the generated shader program among at least one previously compiled shader program and output the retrieved shader program.

The shader program manager 100 can use the key in the step of searching for the same shader program as the generated shader program 1000a. In one embodiment, the shader program manager 100 may generate a key using the information contained in the generated shader program 1000a. In addition, the key generated by the shader program manager 100 may be stored in the cache 400. When the key is stored in the cache, the shader program manager 100 compares the key of the generated shader program 1000a with the key of the shader program stored in the cache 400, thereby obtaining the same shader program as the generated shader program 1000a It can be retrieved from the cache 400.

When the shader program manager 100 searches for the same shader program as the generated shader program 1000a, the shader program manager 100 can output the searched shader program. The shader program manager 100 may output the searched shader program to the graphics processor 300. The shader program manager 100 can output the searched shader program as a binary.

The shader program manager 100 can output the generated shader program 1000a to the compiler 500 when the shader program manager 100 fails to search for the same shader program as the generated shader program 1000a. The compiler 500 can compile the input shader program 1000a to generate a binary. The graphics driver 200 can output the generated binary to the graphics processor 300. [ The generated binaries may be stored in the cache 400. If the shader program manager 100 fails to retrieve the same shader program as the generated shader program 1000a, the key of the generated shader program 1000a may be stored in the cache 400. [ However, it is not limited thereto.

4 is a block diagram of a shader program manager according to an embodiment.

Referring to FIG. 4, the shader program manager 100 according to an embodiment may include a shader memory 110 and a work manager 120.

The graphics command received by the shader program manager 100 may be stored in the shader memory 110. The shader memory 110 may store at least one shader included in the graphics instruction. The shader stored in the shader memory 110 may include a vertex shader and a pixel shader.

In one embodiment, the shader memory 110 may store vertex shaders and pixel shaders that include the source API. The source API may include source code. The shader memory 110 may store the source code of the vertex shader and pixel shader including the source API. The source code for vertex shaders and pixel shaders can be stored in text form. The source code of each of the vertex shader and pixel shader may be stored independently in the TEXT_source space of the shader memory 110. [ However, it is not limited thereto.

In addition, the shader memory 110 may store a vertex shader and a pixel shader including a source API and a compilation API. The compilation API can include compiled code. In the shader memory 110, compile codes of the vertex shader and the pixel shader may be stored. The compile code for vertex shaders and pixel shaders can be stored in text form. The compile code of each of the vertex shader and the pixel shader can be stored independently in the TEXT_ compilation space of the shader memory 110. [

Alternatively, the compilation API may be processed later than the source API when a single shader is received. The source code of the vertex shader and pixel shader independently stored in the TEXT_ source space of the shader memory 110 is copied and the copied source code can be independently stored in the TEXT_ compilation space of the shader memory 110 . However, it is not limited thereto.

When the shader program manager 100 sequentially receives each of the at least one vertex shader and the pixel shader including the source API, the shader program manager 100 stores the received vertex shader and pixel shader in the shader memory 110 Can be stored.

In one embodiment, regardless of whether the source code is stored in the TEXT_source space in the shader memory 110, the shader program manager 100 stores the source code of each of the later received vertex shader and pixel shader in the shader memory 110 in the TEXT_source space. Finally, the source code of the vertex shader and the pixel shader received most recently by the shader program manager 100 among the vertex shader and pixel shader including the source API can be independently stored in the TEXT_ source space in the shader memory 110 .

When the shader program manager 100 sequentially receives each of the at least one vertex shader and the pixel shader including the source API and the compile API, the shader program manager 100 stores the received vertex shader and pixel shader in the shader memory 110).

In one embodiment, regardless of whether the source code (or compiled code) is stored in the TEXT_ compilation space in the shader memory 110, the shader program manager 100 determines whether each of the vertex shaders and pixel shaders Code (or compiled code) in the TEXT_ compilation space in the shader memory 110 independently. When the shader program manager 100 independently stores the source code in the TEXT_ compilation space in the shader memory 110, the source of the vertex shader and the pixel shader independently stored in the TEXT_ source space of the shader memory 110 The code is copied and the copied source code can be stored independently in the TEXT_ compilation space of the shader memory 110. [

In one embodiment, the operation may be omitted by delaying the graphics instruction. In another embodiment, the received shader for the shader program selection may be deferred to omit the shader creation operation that would not be used in the shader program. In another embodiment, the shader being deferred may be a vertex shader and a pixel shader.

The work manager 120 can search for the same shader program as the generated shader program 1000a.

The work manager 120 may include a work memory 121 and a work processor 122.

The work memory 121 may store information used for shader program search.

The work memory 121 may include a vertex shader, a pixel shader, and uniform data information. In one embodiment, work memory 121 may include text and text lengths of vertex shader and pixel shader source code (or compiled code), text and text length of uniform data, compiler version, and GPU version information.

The work processor 122 may search for a shader program. The work processor 122 will be described below with reference to FIG.

5 is a diagram illustrating an example of searching a shader program in a work processor according to an embodiment.

The work processor 122 can search for the same shader program as the shader program 1000a generated from at least one compiled shader program using the information stored in the work memory 121. [

The work processor 122 can perform a search using a key. When searching by using a key, the work processor 122 may include a key generating unit 123 and a key comparing unit 124.

The key generation unit 123 can generate a key using information stored in the work memory 121. For example, the length of the text and text of the vertex shader and pixel shader source code (or compiled code) stored in the work memory 121, the length of the text and text of the uniform data, the compiler version, and the GPU version information are used Can be generated.

The key comparing unit 124 may compare the key generated by the key generating unit 123 with the key of at least one previously compiled shader program. The keys of at least one previously compiled shader program may be stored in the cache 400. When the key is stored in the cache 400, the key comparison unit 124 may compare the key generated by the key generation unit 123 with the key of at least one previously compiled shader program stored in the cache 400 have.

6 is a diagram illustrating an example in which a graphics instruction processing apparatus according to an embodiment searches for and outputs a shader program.

Referring to FIG. 6, the graphics instruction processing apparatus according to an embodiment may be implemented by the shader program manager 100. However, it is not limited thereto.

The shader program manager 100 can output the searched shader program to the graphics driver 200 when searching for a compiled shader program that is the same as the shader program 1000a generated by the work processor 122. [ Alternatively, when the graphics instruction processing device is implemented by the graphics driver 200, the graphics driver 200 may output the searched shader program to the graphics processor 300. [ The retrieved shader program can be output as binary.

The shader program manager 100 can output the generated shader program 1000a to the compiler 500 when the work processor 122 can not retrieve the same compiled shader program as the generated shader program 1000a, The generated shader program 1000a can be compiled in the compiler 500. [ Alternatively, when the graphics instruction processing apparatus is implemented by the graphics driver 200, the graphics driver 200 can output the generated shader program 1000a to the compiler 500, and the generated shader program 1000a Can be compiled in the compiler 500. The compiled shader program 1000b can be used when the work processor 122 searches for the same shader program as the newly generated shader program 1000a. If the work processor 122 fails to retrieve the same compiled shader program as the generated shader program 1000a, the compiled shader program 1000b may be stored in the cache 400. [ The compiled shader program 1000b may be stored in the cache 400 as a binary.

When the work processor 122 searches for a compiled shader program that is the same as the generated shader program 1000a, the shader program can be searched using the key.

If the work processor 122 fails to retrieve a compiled shader program having the same key as the generated shader program 1000a, the key of the generated shader program 1000a may be stored in the cache 400. [ After the generated shader program 1000a is compiled, the compiled shader program 1000b can be stored in the cache 400 as a binary. After the binary is stored in the cache 400, the key of the shader program 1000a stored in the cache 400 may be concatenated with the binary.

7 is a diagram specifically illustrating an example of a process of processing data in the graphics instruction processing apparatus according to an embodiment. However, it is not limited anymore.

8 is a detailed flowchart of a method of processing a graphics command according to an embodiment.

8 may be implemented by a main processor, a GPU, a shader program manager, a graphics driver, or the like. However, it is not limited thereto.

Hereinafter, the case where each step is executed by the shader program manager 100 will be described.

The shader program manager 100 can determine whether a graphics command has been received. If it is determined that a graphics command has been received, the shader program manager 100 can start the following operations. In step 810, the shader program manager 100 may determine whether the received graphics command is a shader program related API.

If it is determined in step 810 that an API other than the shader program-related API has been received, the API other than the shader program-related API may be output directly to the graphics driver 200 without being processed in the shader program manager 100. An existing graphics driver 200 operation may be performed on an API other than the shader program related API output to the graphics driver 200. [

Alternatively, if it is determined in step 810 that the shader program related API has been received, the process proceeds to step 820.

If it is determined in step 820 that the shader program manager 100 has received the shader program creation or deletion API, the shader program manager 100 may allocate or delete space in the shader and shader program related memory in step 821 . In step 821, the shader program manager 100 may allocate or delete space to the shader memory 110 and the work memory 121. [

Alternatively, if it is determined in step 820 that the shader program creation or shader program deletion API has not been received, step 830 may be performed.

If it is determined in step 830 that the shader program manager 100 has received the shader source API, the shader program manager 100 may store the shader including the shader source API in step 831. The shader may be stored in the shader memory 110. The source code of the shader may be stored in the shader memory 110. The source code of the shader may be stored in the TEXT_ source space of the shader memory 110. The source code of each of the vertex shader and pixel shader may be stored independently in the TEXT_source space of the shader memory 110. [ However, it is not limited thereto.

Or if it is determined in step 830 that the shader program manager 100 has not received the shader source API, step 840 may be performed.

If it is determined in step 840 that the shader program manager 100 has received the shader compilation API, the shader program manager 100 may store the shader in step 841. The shader may be stored in the shader memory 110. The shader source code (or compiled code) may be stored in the shader memory 110. The shader source code (or compiled code) may be stored in the TEXT_ compilation space of the shader memory 110. When the source code of the shader is stored, the source code stored in the TEXT_ source space is copied, and the copied source code can be stored in the TEXT_ compilation space of the shader memory 110. The source code of each of the vertex shader and the pixel shader may be stored independently in the TEXT_ compilation space of the shader memory 110.

If the source code is stored in the TEXT_source space in the shader memory 110 in step 841, or if the source code (or compiled code) is stored in the TEXT_compile space, the TEXT_source space or the TEXT_compile space The source code (or the compiled code) of the shader received later by the shader program manager 100 may be stored.

Or if it is determined in step 840 that the shader program manager 100 has not received the shader compilation API, the process proceeds to step 850.

If it is determined in step 850 that the shader program manager 100 has received the shader attach / detach API, the shader program manager 100 sends the shader stored in the shader memory 110 to the work manager 120 in step 851 Connection (or storage). When the shader is connected (or stored) to the work manager 120, the source code (or compiled code) stored in the TEXT_compile space can be connected (or stored) to the work manager 120. When the shader is stored in the work manager 120, the shader program manager 100 may store the source code (or compiled code) in the work memory 121. [ The length of the text and the text of the source code (or compiled code) may be stored in the work memory 121. Or if it is determined in step 850 that the shader program manager 100 has not received the shader attach / detach API, the process proceeds to step 860.

If it is determined in step 860 that the shader program manager 100 has received the uniform data storage API, the shader program manager 100 may connect (or store) the uniform data to the work manager 120 in step 861 have. When the shader is stored in the work manager 120, the shader program manager 100 may store the uniform data in the work memory 121. [ The length of the text and the text of the uniform data can be stored in the work memory 121. [ However, it is not limited thereto.

Or if it is determined in step 860 that the shader program manager 100 has not received the uniform data storage API, the process proceeds to step 870.

If it is determined in step 870 that the shader program manager 100 has received the shader program link API, the shader program manager 100 uses the information connected (or stored) to the work manager 120 in step 871 Key can be generated. The shader program manager 100 determines the length of the text and text of the at least one shader source code connected to (or stored in) the work manager 120, the length of the text and text of the uniform data, And the GPU version information.

Alternatively, if it is determined in step 870 that the shader program manager 100 has not received the shader program link API, the existing graphics driver 200 operation may be performed on the received graphics API on the received API.

If it is determined in step 872 that a shader program having the same key as the key generated in step 871 is searched, the shader program manager 100 may output the searched shader program in step 873. The existing graphics driver 200 operation can be performed on the output shader program. The key of the shader program can be stored in the cache. The retrieved shader program can be output as binary.

Or if it is determined in step 872 that the shader program having the same key as the key generated in step 871 has not been found, the shader program manager 100 determines whether the shader program has been connected (or stored) to the work manager 120 Information necessary for compiling the shader program can be generated and the compile request can be made to the graphics driver 200. [

9 is a flowchart of a method of processing a shader program related API by a graphics driver according to an exemplary embodiment. 10 is a flowchart of a method of processing a shader program related API by a shader program manager according to an exemplary embodiment.

Hereinafter, Fig. 10 will be described in comparison with Fig.

10, when the shader program manager 100 receives at least one vertex shader and at least one pixel shader, the vertex shader and the pixel shader are processed by the shader program manager 100 in the order of receiving the shader .

In FIG. 9, the shader program manager 100 can process only the shader creation API and the source code storage API in FIG. 10, except that the graphics driver 200 processes all the APIs included in the shader every time a shader is received . You can suspend processing for other APIs contained in the shader. The shader program manager 100 may process only the shader creation API and the source code storage API until the shader program link API is received and suspend processing for the other APIs. However, it is not limited thereto.

In FIG. 10, when the shader program manager 100 receives the shader program link API, it can process the API included in each of the vertex shader and pixel shader received last. Vertex shaders and pixel shaders may include a source API and a compilation API. When the vertex shader and the pixel shader include the source API and the compile API, the shader program manager 100 can process the API except the compilation API. After the API other than the compiling API is processed, the compiling API can be processed in the graphics driver 200. [

Referring to FIG. 10, when the graphics driver 200 processes the compile API command, the vertex shader and the pixel shader may be compiled in the compiler 500. Each of the vertex shader and pixel shader compiled in the compiler 500 may be a vertex shader and a pixel shader that are most recently received by the shader program manager 100. When the vertex shader and the pixel shader are compiled, the graphics driver 200 can generate the shader program 1000b including the compiled vertex shader and the pixel shader. The existing graphics driver 200 operation can be performed on the generated shader program 1000b.

Some embodiments may also be implemented in the form of a recording medium including instructions executable by a computer, such as program modules, being executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

Also, in this specification, the term "part" may be a hardware component such as a processor or a circuit, and / or a software component executed by a hardware component such as a processor.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

Claims (15)

A method for processing a graphics command,
Receiving the graphics command from an apparatus executing an application;
Selecting at least one shader included in the graphics instruction to be processed in the graphics processor;
Generating a shader program using at least one selected shader;
Searching for a shader program identical to the generated shader program among at least one previously compiled shader program; And
Outputting the retrieved shader program;
/ RTI > The method according to claim 1,
Wherein the selecting step selects a vertex shader and a pixel shader that include a source instruction and a compile instruction. The method according to claim 1,
Wherein the selecting includes selecting a vertex shader and a pixel shader that include the source code and the compiled code, and which are received most recently. The method of claim 3,
Wherein the generating the shader program comprises generating the shader program using the vertex shader, the pixel shader, and the uniform data. The method according to claim 1,
Wherein the searching comprises: generating a key including text and text length of the at least one shader, text and text length of uniform data, compiler version, and GPU version information; And
Searching by using the generated key;
/ RTI > The method according to claim 1,
Wherein the outputting step outputs a binary of the searched shader program. A graphics instruction processing apparatus comprising:
A graphics processor for receiving graphics commands from an apparatus executing an application, selecting at least one shader to be processed in a graphics processor included in the graphics command, generating a shader program using the selected at least one shader, A processor for searching for a shader program identical to the generated shader program among at least one shader program and outputting the retrieved shader program; And
A cache storing previously compiled shader programs;
. 8. The method of claim 7,
Wherein the processor is to select a vertex shader and a pixel shader that include compiled code. 8. The method of claim 7,
Wherein the processor comprises a command and a compile instruction, and selects a vertex shader and a pixel shader that are to be received most recently. 10. The method of claim 9,
Wherein the processor is to generate a shader program using the vertex shader, the pixel shader, and the uniform data. 8. The method of claim 7,
The processor generates a key using data including text and text length of the at least one shader, text and text length of the uniform data, compiler version, and GPU version information, and using the generated key Device. 8. The method of claim 7,
Wherein the cache stores information comprising keys and binaries corresponding to compiled shader programs. 8. The method of claim 7,
Wherein the processor does not perform compilation even upon receipt of a shader that includes compiled code. A graphics processor for receiving graphics commands from an apparatus executing an application, selecting at least one shader to be processed in a graphics processor included in the graphics command, generating a shader program using the selected at least one shader, A graphics driver for searching for a same shader program as the generated shader program among the shader programs and outputting the retrieved shader program; And
A cache storing previously compiled shader programs;
Gt; GPU. ≪ / RTI > A computer readable non-transitory recording medium having recorded thereon a program for causing a computer to execute the method of claim 1.

Images