Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111303 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 84564 invoked from network); 3 Aug 2020 20:42:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 3 Aug 2020 20:42:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BAF8D180532 for ; Mon, 3 Aug 2020 12:40:14 -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=-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_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f54.google.com (mail-io1-f54.google.com [209.85.166.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 3 Aug 2020 12:40:14 -0700 (PDT) Received: by mail-io1-f54.google.com with SMTP id t15so30837417iob.3 for ; Mon, 03 Aug 2020 12:40:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OVmu1mpOrjuAaIvG+1DO/i6sps4B6YnH1J+xJDOlHxo=; b=XVNp5UOOu2QyRe3paGY//yWpxHmx89xQsTPaiCHH/G/LG9p87W3yTJbnDlj0zs6eRA 9nwKRHD98CVDwHDBT3ZgzVTBh5mAZjA+iVC1kn+OHPLDuSIrKpMjptQeBKZ1gHqGJSJx e3XcOANOLGxMzqLDzU3TUu2giHyOuhqBWWrtg2bXmdf/n6QJQPjBLLTBL6E44Q2F1KEa qjwvUWLIFEI4u8NZFN4A561oLk5J1stWEr+d+HG3j9qsDpvZpKHjKl2ZSYoejk7tFA8/ uc+Wz1kPetUgDsc7hbezAsb5QqkUKhI+JypYKlaS0slIWbGDGRLzYumObhyxP7r8lIah LbAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OVmu1mpOrjuAaIvG+1DO/i6sps4B6YnH1J+xJDOlHxo=; b=de2L+AG5WChr9eUcR/4PpIXGtCaOn38Gm7yt3ZbkN8gm9BYS3oor4oIVQVbx6xTP1T wet7ZXYRtyJOjKRnxL7e6rZ1Ij74K1wSa9cO/TkuRcTGkJUTPGmR+gL7n/xTCSb0lie7 ACI9y44gROja5B19QDkDDNUxvh6UkNA0oxjKyIE7k9E6AbGzNoOMnQ5rYzjIN8WcLHhw CgIj5axzMoadF/koeCeFt0mo1qjpFUX9pi9fvziMNNmYYK608gQNvzajBBaxZ2HV0hAf X/3TgINEK3yiPnreVlTOcnva+eTIOqZ39I2iV/arTFEzH48RZY12br4unGV4uAJIkwxx og6Q== X-Gm-Message-State: AOAM530Rwd/kRBG877Ma+GzIRZEyoiAw2t0F7sMRFPUKj6yoOaXh8TOf BGigaVAJFvEcpKBxQ7B9wDbpu/CS X-Google-Smtp-Source: ABdhPJybiDU9ISCB7KKvQM7d+0mL5yoSbhv7IQ1nxGVkzlAeUqkrZuQ8iUJPWX0W5i8QkEifE+p7HQ== X-Received: by 2002:a05:6638:1489:: with SMTP id j9mr1550817jak.22.1596483609954; Mon, 03 Aug 2020 12:40:09 -0700 (PDT) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com. [209.85.166.50]) by smtp.gmail.com with ESMTPSA id y80sm11417199ilk.82.2020.08.03.12.40.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Aug 2020 12:40:09 -0700 (PDT) Received: by mail-io1-f50.google.com with SMTP id z6so39816899iow.6 for ; Mon, 03 Aug 2020 12:40:08 -0700 (PDT) X-Received: by 2002:a05:6638:621:: with SMTP id h1mr1436908jar.143.1596483608361; Mon, 03 Aug 2020 12:40:08 -0700 (PDT) MIME-Version: 1.0 References: <0e6dff76-0434-4d21-dc08-1fa1bf41a1e0@gmail.com> In-Reply-To: <0e6dff76-0434-4d21-dc08-1fa1bf41a1e0@gmail.com> Date: Mon, 3 Aug 2020 20:39:32 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Stanislav Malyshev Cc: Benjamin Eberlei , PHP Internals , Dmitry Stogov , Nikita Popov Content-Type: multipart/alternative; boundary="0000000000005dda1a05abfe4e12" Subject: Re: [PHP-DEV] @@Jit Attribute Considerations From: phpmailinglists@gmail.com (Peter Bowyer) --0000000000005dda1a05abfe4e12 Content-Type: text/plain; charset="UTF-8" On Mon, 3 Aug 2020 at 19:52, Stanislav Malyshev wrote: > I think turning JIT off is a valid use case, the rest looks much more > iffy. I am not sure we want to let people tell the engine to JIT certain > functions - are there a lot of cases where the engine wouldn't do it but > it's actually the right thing to do? > Wouldn't a use case be profiling code, to see if JIT makes a difference to a specific function? So I can profile with JIT disabled globally and @@JIT on specific code, modify my code and see if it improves the JIT performance? I'm basing this on my experience with the @jit annotation in Numba ( http://numba.pydata.org/) where it's useful to see the effect on small pieces of code. Peter --0000000000005dda1a05abfe4e12--