如果你被允许运行真正的本地二进制文件，那么这是你的编译器:

https://github.com/ircmaxell/php-compiler

这是一个用PHP编写的PHP编译器!

It compiles PHP code to its own VM code. This VM code can then either be interpreted by its own interpreter (also written in PHP, isn't that crazy?) or it can be translated to Bitcode. And using the LLVM compiler framework (clang and co), this Bitcode can be compiled into a native binary for any platform that LLVM supports (pretty much any platform that matters today). You can choose to either do that statically or each time just before the code is executed (JIT style). So the only two requirements for this compiler to work on your system is an installed PHP interpreter and an installed clang compiler.

如果您不允许运行本机二进制文件，您可以使用上面的编译器作为解释器，让它解释自己的VM代码，但是这会很慢，因为您运行的PHP解释器本身运行在PHP引擎上，因此您有“双重解释”。

PHP代码有几个“编译器”。它们中的大多数不支持所有PHP特性，因为这些特性必须在运行时进行解释。

我们正在使用Phalanger - http://www.php-compiler.net/ -它甚至支持那些肮脏的PHP动态特性，并且仍然能够将它们编译为。net程序集，可以作为一个独立的DLL分发。

见5.5。使用集成的OPcache模块，在共享内存中的易失性，更好的性能和php的动态原则保持不变。

http://www.php.net/manual/en/opcache.installation.php

PHP不像许多程序那样真正被编译。您可以使用Zend的编码器使其不可读。

在php 7中有php ini选项opcache。File_cache，用于将字节码保存到指定文件夹中。In可能对In php cli脚本有用，这些脚本被“编译”并保存在特定的文件夹中，以便优化重用。

Opcache，它不是编译，而是类似的东西。

Actually, the Just-In-Time compiler introduced with PHP 8 does in fact compile PHP. Strangely enough, it doesn't really speed up CMS based websites (e.g. WordPress), however, it does open the doors for PHP to compete with the likes of C++. For more information, see the RFC behind the JIT implementation here: https://wiki.php.net/rfc/jit. Also, Matthew Weir O'Phinney has posted a number of insightful blogs that shed light on its capabilities. Start reading here: https://www.zend.com/blog/exploring-new-php-jit-compiler.