rfc:direct-execution-opcode

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
rfc:direct-execution-opcode [2020/12/10 12:19] – chopinsrfc:direct-execution-opcode [2020/12/10 12:24] – chopins
Line 14: Line 14:
 When executing, judge whether the loaded PHP file is an opcode file based on the flag. if no flag, will run as it is now.If is opcode file will direct execution without check php source file. When executing, judge whether the loaded PHP file is an opcode file based on the flag. if no flag, will run as it is now.If is opcode file will direct execution without check php source file.
  
-**includes** and **require** will load opcode file. So if you include opcode files, the source code must use the compiled file path instead of the source file.+The **includes()** **includes_once()** and **require()** **require_one()** can load opcode file. So if you include opcode files, the source code must use the compiled file path instead of the source file path.
  
 Change function to: Change function to:
Line 32: Line 32:
  
 php--->load code--->compile to opcode--->save to cache system directory-->same path file-->**copy cache file to the specified path** php--->load code--->compile to opcode--->save to cache system directory-->same path file-->**copy cache file to the specified path**
 +
 +new opcode file format like below:
 +
 +<PHP>
 +<?phpo{phpversionid}OPCACHE575d367cc725713f6f170910d6e9ee5e-------BINARY CONTENT OF OPCODE----
 +</PHP>
  
 **opcache exec process:** **opcache exec process:**
rfc/direct-execution-opcode.txt · Last modified: 2021/04/23 18:07 by imsop

Page Tools