Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:125649 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 374C41A00BD for ; Fri, 20 Sep 2024 21:09:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1726866714; bh=y2TWV7ZEfnAo2V6V+Nt1DSn0OYNrsqzdOqwc8T/zwhA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=izLk3ewV7I1ztQR8oIQtCERAjG/xlzxXnzc3Xna0MAkxDksx1aL3oorV5UhKAL4tN 1/5Clzrn3k9pZXCz+d/P/LaucKH40LTuASh+1tEAcz9a2cv2Uis1AeV+scrg67i4dR OfltwpxUinY5jU08/+TOvm8SKW4na8L/nTNQJHJ6Lfgy2CevWBSxnRlAn2BTQY62KN 8hirL5YtrJMPQCVOBWeMWuMYOaRHQo9IqA7sxTnvgLNEhKvyj0FkCOzsX9UYoHAYNQ PrEEL6/mcdKmSIZDzmwuEOTvi7jh2kVbnK+rEm9IZSIBfv+tfEw1moQftHIRvzDQwx JManJWSAuRcPg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 006D918004A for ; Fri, 20 Sep 2024 21:11:54 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: * X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_50,DMARC_NONE, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f53.google.com (mail-ot1-f53.google.com [209.85.210.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 20 Sep 2024 21:11:53 +0000 (UTC) Received: by mail-ot1-f53.google.com with SMTP id 46e09a7af769-710da656c0bso1054268a34.0 for ; Fri, 20 Sep 2024 14:09:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726866586; x=1727471386; 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=y2TWV7ZEfnAo2V6V+Nt1DSn0OYNrsqzdOqwc8T/zwhA=; b=Tb9x7n+9bs5fvIj1n0mcqjpXzPTZfXHP1D4cwY1cQT+djo6+bUg4sK7RLODr22XHmY rjQmILvC9/ERLxYoV2oygIUyYVOCRdGiENfeHDl7FuHYf8rMn6jtjqIPNb9vB7rGQvVj qnRsgVpUow983Z5NjamOEky8dhGcZ7FrADrfXIhEi8E2DAGJfICGZJGsxUC+jxjgpxX8 2GW0xyOTcG5BERoW7iJLVxrqaWNfrls2zrC9lVWViaqqBnbldrqCRV8cimAXD65pEyVQ RQGFNcN93tPtOcWzWrz0W8j867gem/Y2tpJWnXDBmT5cjk0qshnMbj/FUd06bFzdQNpa QSfw== X-Forwarded-Encrypted: i=1; AJvYcCV4kj1ZCWPypGHpWcvD9RUQiunugox79y/bI0/N4g7h4WjfEakNTFGhReobiTkKdIDRzgmzOO99oxk=@lists.php.net X-Gm-Message-State: AOJu0Yxz8Y4rqEMa+yqQve0W4CgGhE3iaAHszcsFw60nEnkxq+ojufK9 /huFMt/X2/IUXR1NyF2Fn/eh60T/nhrrjvuMFK0QkHdMD13oPamyQgzjZ34QYhprmQDsYcMAECh D10m/yqj2dvuXh3/wUgCyBy6VinE= X-Google-Smtp-Source: AGHT+IG5mQOp1uwZE591kzQHPIMh2jc5ERemV2SbYwVHYdMdiSv5Ti6nz09kc0aIZpTDYNmLOc1smZ96oUC2B7xCiug= X-Received: by 2002:a05:6808:2e49:b0:3e0:4504:4b70 with SMTP id 5614622812f47-3e271bb0d57mr3515470b6e.23.1726866585790; Fri, 20 Sep 2024 14:09:45 -0700 (PDT) Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 References: <8D420123-4ECF-48FD-A9C3-F80C60457A37@newclarity.net> <7EA884D2-0F37-4BF1-AC97-DB6953C944E6@automattic.com> <8A970628-C287-4584-8E44-7708E38142F7@automattic.com> In-Reply-To: <8A970628-C287-4584-8E44-7708E38142F7@automattic.com> Date: Fri, 20 Sep 2024 22:09:34 +0100 Message-ID: Subject: Re: [PHP-DEV] Zephir, and other tangents To: Dennis Snell Cc: Arvids Godjuks , Hammed Ajao , Rob Landers , Adam Zielinski , Mike Schinkel , PHP internals Content-Type: multipart/alternative; boundary="0000000000006bb4490622937522" From: bukka@php.net (Jakub Zelenka) --0000000000006bb4490622937522 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Fri, Sep 20, 2024 at 9:36=E2=80=AFPM Dennis Snell wrote: > > On Sep 20, 2024, at 1:21 PM, Jakub Zelenka wrote: > > Hi, > > On Fri, Sep 20, 2024 at 6:32=E2=80=AFPM Dennis Snell > wrote: > >> >> My goal in sharing here is to help better represent my own perspective o= f >> WordPress=E2=80=99 needs based on what I=E2=80=99ve seen. It=E2=80=99s l= ong been on my list to >> propose a WASM RFC, but because I personally haven=E2=80=99t had the pri= ority >> available to get an implementation working I haven=E2=80=99t done so. It= =E2=80=99s my >> impression from the documentation that the purpose of these email thread= s >> w.r.t. RFCs is to gather interest and input before any RFC would be put >> together, to hold these discussions before anyone commits any major time= to >> it. >> > > Is your objective to support building PHP to wasm32-wasi target like it > was proposed here: https://github.com/php/php-src/pull/10457? If so, the > main issue with that was inability to do the zend_bailout as wasm does no= t > support currently support setjmp and longjmp. Otherwise it's mostly about > disabling some functionality. > > > It=E2=80=99s the other way around. We=E2=80=99ve been having a great time= already building > PHP as a WASM binary - > Ah ok I just did a bit of research and checking your wordpress-playground and it uses emscripten which actually integrates extensions to WASM (currentl proposed https://github.com/WebAssembly/exception-handling ) or it can JavaScript based support as described in https://emscripten.org/docs/porting/setjmp-longjmp.html . So it's not actually an issue in your case. Officially PHP can still cannot be build to the official wasm32-wasi target but as I understand it's not such a big issue because there are already viable alternatives. Cheers Jakub --0000000000006bb4490622937522 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Fri, Sep 20, 2024 at 9:36=E2=80=AFPM Dennis Sne= ll <dennis.snell@automatt= ic.com> wrote:

On Sep 20, 2024, at 1:21 PM, Jakub Zelenka <bukka@php.net> wrote:

Hi,

On Fri, Sep 20, 2024 at 6:32=E2=80=AF= PM Dennis Snell <dennis.snell@automattic.com> wrote:

My goal in sharing here is to help better represent my own perspective= of WordPress=E2=80=99 needs based on what I=E2=80=99ve seen. It=E2=80=99s = long been on my list to propose a WASM RFC, but because I personally haven= =E2=80=99t had the priority available to get an implementation working I ha= ven=E2=80=99t done so. It=E2=80=99s my impression from the documentation th= at the purpose of these email threads w.r.t. RFCs is to gather interest and= input before any RFC would be put together, to hold these discussions befo= re anyone commits any major time to it.

Is your objective to support building PHP to wasm32-wasi tar= get like it was proposed here:=C2=A0https://github.com/php/php-sr= c/pull/10457? If so, the main issue with that was inability to do the z= end_bailout as wasm does not support currently support setjmp and longjmp. = Otherwise it's mostly about disabling some functionality.

It=E2=80=99s the other way around. We=E2=80=99ve been having a great t= ime already building PHP as a WASM binary -=C2=A0

Ah ok I just did a bit of research and checkin= g your wordpress-playground and it uses emscripten which actually integrate= s extensions to WASM (currentl proposed=C2=A0https://github.com/WebAssembly/exception-ha= ndling ) or it can JavaScript based support as described in=C2=A0https://emscr= ipten.org/docs/porting/setjmp-longjmp.html . So it's not actually a= n issue in your case. Officially PHP can still cannot be build to the offic= ial wasm32-wasi target but as I understand it's not such a big issue be= cause there are already viable alternatives.

Cheer= s

Jakub
--0000000000006bb4490622937522--