Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109629 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 10464 invoked from network); 14 Apr 2020 15:30:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 14 Apr 2020 15:30:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1EFA51804C3 for ; Tue, 14 Apr 2020 07:00:13 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_20,SPF_HELO_NONE, SPF_NEUTRAL autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS20694 188.94.24.0/21 X-Spam-Virus: No X-Envelope-From: Received: from scarlet.netpirates.net (scarlet.netpirates.net [188.94.27.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 14 Apr 2020 07:00:13 -0700 (PDT) Received: from p5de2c6cc.dip0.t-ipconnect.de ([93.226.198.204] helo=[192.168.178.42]) by scarlet.netpirates.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jOM6m-0006ng-1d for internals@lists.php.net; Tue, 14 Apr 2020 16:00:12 +0200 To: internals@lists.php.net References: <0ddd2987-644b-6fec-2670-2b6f366290e2@php.net> Reply-To: internals@lists.php.net Message-ID: <2c99eb72-b177-cddf-e35c-d2ea3cdfaed2@php.net> Date: Tue, 14 Apr 2020 16:00:11 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <0ddd2987-644b-6fec-2670-2b6f366290e2@php.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] opcache.jit directive should be split up From: sebastian@php.net (Sebastian Bergmann) Am 14.04.2020 um 15:53 schrieb Sebastian Bergmann: > The value for opcache.jit is currently a sequence of four digits, "5021" > for instance. This would activate JIT optimizations based on static type > inference and inner procedure analyses (Optimization Level), JIT > optimization of all functions on load of the respective sourcecode file > (Trigger), global linear-scan register allocator (Register Allocation), > and AVX instruction generation (CPU-Specific Optimization Flags). Sorry for the noise, but it is more confusing than I thought just a couple of minutes ago. The RFC reads > Consists of 4 decimal digits - CRTO and then lists the individual parts in reverse order (OTRC).