6f6fd27d2f
Test case "ext/standard/tests/array/range.phpt" failed on ARM64 machine only under RELEASE mode. How to reproduce it: ``` ./buildconf -f; ./configure; make -j 128 make test TESTS="-d opcache.enable=1 -d opcache.enable_cli=1 ext/standard/tests/array/range.phpt" ``` Root cause: I suspect the root cause is that on ARM64 machine, PHP RELEASE mode produces different values for internal function range() compared to DEBUG mode. Take the downsized test case downsize-range.php [1] as an example. We applied the check-element.diff patch to check the original values. Note that we print out the floating point numbers with precision 16. From the outputs in file output.md, we can see the 7-th and 9-th elements are different between RELEASE and DEBUG. To be honest, I didn't get where such difference comes from and probably this is due to different compilation options used by RELEASED and DEBUG. Fix: After commit [2], serialize_precision is used for var_dump(). As a result, the pre-set "precision=14" didn't work actually. In this patch, we turn to set serialize_precision as 14 and therefore the difference between RELEASE and DEBUG can be eliminated. Note-1: this failue didn't occur on x86 machine. Note-2: in my local test, this is the only test case which behaves differently on ARM64 machine under RELEASE and DEBUG mode. [1] https://gist.github.com/shqking/0d55abf8dbaafde4a00ea9304e71f06b [2] https://github.com/php/php-src/commit/a939805 Change-Id: I9293e990925590f8d7cfb2462d8d760abf76069f
The PHP Interpreter
PHP is a popular general-purpose scripting language that is especially suited to web development. Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. PHP is distributed under the PHP License v3.01.
Documentation
The PHP manual is available at php.net/docs.
Installation
Prebuilt packages and binaries
Prebuilt packages and binaries can be used to get up and running fast with PHP.
For Windows, the PHP binaries can be obtained from
windows.php.net. After extracting the archive the
*.exe files are ready to use.
For other systems, see the installation chapter.
Building PHP source code
For Windows, see Build your own PHP on Windows.
For a minimal PHP build from Git, you will need autoconf, bison, and re2c. For a default build, you will additionally need libxml2 and libsqlite3. On Ubuntu, you can install these using:
sudo apt install -y pkg-config build-essential autoconf bison re2c \
libxml2-dev libsqlite3-dev
Generate configure:
./buildconf
Configure your build. --enable-debug is recommended for development, see
./configure --help for a full list of options.
# For development
./configure --enable-debug
# For production
./configure
Build PHP. To speed up the build, specify the maximum number of jobs using -j:
make -j4
The number of jobs should usually match the number of available cores, which
can be determined using nproc.
Testing PHP source code
PHP ships with an extensive test suite, the command make test is used after
successful compilation of the sources to run this test suite.
It is possible to run tests using multiple cores by setting -jN in
TEST_PHP_ARGS:
make TEST_PHP_ARGS=-j4 test
Shall run make test with a maximum of 4 concurrent jobs: Generally the maximum
number of jobs should not exceed the number of cores available.
The qa.php.net site provides more detailed info about testing and quality assurance.
Installing PHP built from source
After a successful build (and test), PHP may be installed with:
make install
Depending on your permissions and prefix, make install may need super user
permissions.
PHP extensions
Extensions provide additional functionality on top of PHP. PHP consists of many essential bundled extensions. Additional extensions can be found in the PHP Extension Community Library - PECL.
Contributing
The PHP source code is located in the Git repository at git.php.net. Contributions are most welcome by forking the GitHub mirror repository and sending a pull request.
Discussions are done on GitHub, but depending on the topic can also be relayed to the official PHP developer mailing list internals@lists.php.net.
New features require an RFC and must be accepted by the developers. See Request for comments - RFC and Voting on PHP features for more information on the process.
Bug fixes do not require an RFC but require a bug tracker ticket. Open a
ticket at bugs.php.net and reference the bug id using
#NNNNNN.
Fix #55371: get_magic_quotes_gpc() throws deprecation warning
After removing magic quotes, the get_magic_quotes_gpc function caused a
deprecated warning. get_magic_quotes_gpc can be used to detect the
magic_quotes behavior and therefore should not raise a warning at any time.
The patch removes this warning.
Pull requests are not merged directly on GitHub. All PRs will be pulled and pushed through git.php.net. See Git workflow for more details.
Guidelines for contributors
See further documents in the repository for more information on how to contribute:
Credits
For the list of people who've put work into PHP, please see the PHP credits page.