Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119395 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 39595 invoked from network); 23 Jan 2023 13:07:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Jan 2023 13:07:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B7320180088 for ; Mon, 23 Jan 2023 05:07:25 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-pl1-f174.google.com (mail-pl1-f174.google.com [209.85.214.174]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 23 Jan 2023 05:07:25 -0800 (PST) Received: by mail-pl1-f174.google.com with SMTP id p24so11287947plw.11 for ; Mon, 23 Jan 2023 05:07:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XkHTqO1NuLe/B5wjfz9EA8AKSb4B/yPelVRqIq2WJ4o=; b=jS7uRWThRn6VzoZLcbBbak8b2nlEqjGa9efNB4XUToBmG53glIzKCp9sihqolsSFE7 qCIn8urk36YzcEbMcv2Pcks9Aa3cVPAmwWMK5EwNOoX0Kjzgk6c5US4lATajqSEQdVUl WeNB3BkKKdb14ZFE7Db/4rrn49oE076cqwTO7OEGSA+3WZOgx6D2mHWDDGVitIwcl/Ld xctsIK+7G0solkx+uUIcLyJnOkxNQDh3YDT1qZOKOxbivI7B7FN88GAe+O1BdB436P32 G+CqzGpJseRSjNFGlIlDLmnu65+sF+yziF6RbdwrrdYF+n79OGWNs0AnrjXrtoRLslBy um1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XkHTqO1NuLe/B5wjfz9EA8AKSb4B/yPelVRqIq2WJ4o=; b=3q+Tg33kfw7M/ZCwfy9V2bR59gv9rZDh3NgGk72MOa9NFSTU5FZ9hY4/GjW8yknIfq w2mbkBLHvddMMUVknObmFqsQHRRngAugOnh4tcGCxPC7vF8To9sIVVa7zmN+7janY8pm bEv3qm373r7l+5Dhfi9nSdjHGBhO7QfuU+qw8RpJ/Du8Jw/qqkXUsffR/2syVryvNJ9w psd5moXZwYwOFJCSDcLA3SNucGWIacyiacTbMFi6KwdrE5A5dsZ3a7PHBd1fc5U4DR0Q hg6ZLqkrKccgkuYeQPvnkhr1p06EZgkzEf6uTE/BPGV+QvIkrO7xdZ47tUITQlwbZODm uokQ== X-Gm-Message-State: AFqh2ko5PpdFhvRNKPKVxIjWz0/QEgFPCB0BCOt76mmaJTdcBCFfS3mV O17wlGfNu5HeJJ05OL/wrOr79kgCKyqtO0G3870= X-Google-Smtp-Source: AMrXdXtcbPXMw3uWC7P91cUTDmLlWhD+MB9lRlDwE9ZCa8nE412EgGr7Fgn4duzwzEXXqt1fm1hXfj7R2a+YIJYJGM8= X-Received: by 2002:a17:902:c405:b0:194:5de4:52b5 with SMTP id k5-20020a170902c40500b001945de452b5mr2372454plk.14.1674479244451; Mon, 23 Jan 2023 05:07:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 23 Jan 2023 13:07:13 +0000 Message-ID: To: Jordan LeDoux Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000008ca3e405f2ee1492" Subject: Re: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators From: george.banyard@gmail.com ("G. P. B.") --0000000000008ca3e405f2ee1492 Content-Type: text/plain; charset="UTF-8" On Fri, 20 Jan 2023 at 19:44, Jordan LeDoux wrote: > I don't see a section in the RFC about JIT or anything related to OpCache, > but I know from experience with the Operator Overloads RFC that there are > several architecture specific assembly optimizations for ++ and --. Have > these been considered, and how will they be impacted? > The only assembly specific code is for integer increments/decrements, as those are not affected by this RFC there is no impact to them. Best regards, George P. Banyard --0000000000008ca3e405f2ee1492--