Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130211
Precedence: list
MIME-Version: 1.0
Date: Sun, 01 Mar 2026 15:25:17 +0100
To: Michael Wallner <mike.php.net@gmail.com>
Cc: Michael Wallner <mike@php.net>, PHP Internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Discussion] SIMD-Accelerated CRC via crc-fast
 for ext/hash
In-Reply-To: <522BCAA7-590D-4268-8F8A-4D7B95C71EE5@gmail.com>
References: <CALJZF3jT2fwdP1Sg6uDn71hvJnTaHZqKrTqm1jQh2pNi-bpcnQ@mail.gmail.com>
 <e70a4db113cfcd215e7bb0692909f6ba@bastelstu.be>
 <522BCAA7-590D-4268-8F8A-4D7B95C71EE5@gmail.com>
Message-ID: <9ac9837d4b5b0a03bc0fdd8a47dfeb7c@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2026-02-23 22:49, schrieb Michael Wallner:
> I’d prefer not to split this up, unless there’s strong demand for that 
> in further discussion.

It definitely is two different proposals, so while they may be combined 
into a single RFC document and discussion, it must at least be two 
separate primary votes (see 
https://github.com/php/policies/blob/main/feature-proposals.rst#required-majority). 
I'm also noting that the current voting widget still contains the 
$feature placeholder.

I also consider it important that each of the proposals gets the same 
treatment with regard to visibility in the RFC text. Currently the RFC’s 
focus is the introduction of the crc-fast library, while the new 
algorithms only get a “passing mention”. However as I mentioned before, 
the latter is the more significant change from a PHP developer’s PoV.

To give a specific example from the RFC (Highlighting original):

> When --with-crc-fast is not specified or libcrc_fast is not installed, 
> PHP builds and behaves *exactly as it does today* with the addition of 
> the new CRC-64 algorithms implemented without hardware acceleration.

The “exactly as it does today” together with the “When enabled, the 
following changes take effect:” introduction of the section, still 
heavily implies that the new algorithms are dependent on the library 
being used.

Best regards
Tim Düsterhus