Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91825 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34530 invoked from network); 21 Mar 2016 20:24:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Mar 2016 20:24:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=dz@heroku.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dz@heroku.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: dz@heroku.com X-Host-Fingerprint: 74.125.82.53 mail-wm0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:37021] helo=mail-wm0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 32/D0-29631-39850F65 for ; Mon, 21 Mar 2016 15:24:52 -0500 Received: by mail-wm0-f53.google.com with SMTP id p65so136874276wmp.0 for ; Mon, 21 Mar 2016 13:24:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heroku-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jlDaS4H9GWzkHUCQ0qHQ1YU3AgQqcRx0yLkomq7KB+g=; b=yrE+uuMj0/n0GmAceSy8mvja4jCtfQXKx9eArVjUGKYBx0lvdPSjJ24tHEwvlJCmIu lFsJw4E5MzC9qTe6u1WLsaN+wnuI5u+QFa9FAK3ECHpI67T4WIr0A3zAhUBsgrM81MLN 1Gy3bpYk6CRoOlYur72F/2KweZ5FPlWLyjMUpZgU1IQVKve4vbJUOXGmsYAPa2oFhpYY VTMj7IKesq8FYqcBetjeGPOObPLz28rU/mkuxJ2ciEMIBE7FyBaAwmtkAsacd89BrNsI +X9fxLTmUAQY6d/5Mv2tDHYScEc+VtYWCaZte2vcKqvoIPGWHhD6ij3gXkk/l6c5tZP5 ccUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jlDaS4H9GWzkHUCQ0qHQ1YU3AgQqcRx0yLkomq7KB+g=; b=exFP1L8czKKGIKakDb++cBPfGeqAOy8jcKND16r93tW+4lVsWBZlMEHZspRp7+XOgK TRmHv88FKey+YscSrgutzGvYo+umAzWDcEapx0GT6LE1+8uv9QqejnVuHdPR0XIJegWJ IsRV6aipSPDWxRGmPI02ujwiuuP3wKPDkSpg5yLUm2BfsrOwzB3rBb99kgvLJB0XoPTt QfC3dC/WgWR2GN1Vc/FM1WMjAbijBa4uCk/t4jTPkbtmud4+tcuq8+/Kv4rQPbMbDbIe QBgWjBZhpswQmVFVKo8KEjskKslDRQSbwzbVt/QxD+HiJSP6o/PlWvfyGxJrZNeR05kW jaFQ== X-Gm-Message-State: AD7BkJLny0QsQl8ou3zE5qPuN1el0kSLe+wqtj+J11Sq284FSDSjbKxFfG9xb5zoJbf0Brh/ X-Received: by 10.194.83.134 with SMTP id q6mr32196845wjy.131.1458591889422; Mon, 21 Mar 2016 13:24:49 -0700 (PDT) Received: from [192.168.19.20] (ipb21b5588.dynamic.kabel-deutschland.de. [178.27.85.136]) by smtp.gmail.com with ESMTPSA id fv6sm26970993wjc.12.2016.03.21.13.24.47 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 21 Mar 2016 13:24:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) In-Reply-To: Date: Mon, 21 Mar 2016 21:24:46 +0100 Cc: Anatol Belski , Christoph Becker , Pierre Joye , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <55B0CADD.8000807@gmx.de> <55B136BE.8010006@gmx.de> <046401d0c644$9cf76880$d6e63980$@belski.net> <55B2B78A.4080202@gmx.de> <048001d0c665$ed19ec40$c74dc4c0$@belski.net> <55B2D779.9090409@gmx.de> <04d301d0c6e5$6b28f0c0$417ad240$@belski.net> <55B3B2E6.7080905@gmx.de> <056e01d0c7d9$b1edd990$15c98cb0$@belski.net> <55B559C7.9060304@gmx.de> <064301d0c85f$5260ac60$f7220520$@belski.net> <55C008B1.2050008@gmx.de> <05ec01d0ce97$4ee7c4e0$ecb74ea0$@belski.net> <55C09EE2.7010400@gmx.de> <063f01d0cec2$91b9baf0$b52d30d0$@belski.net> <55C0F908.2050708@gmx.de> <068e01d0cefb$6ffba3e0$4ff2eba0$@belski.net> <016e01d17ef7$cd8a2660$689e7320$@belski.net> <25D67B35-88FF-4A5C-9421-BAF482B32A96@heroku.com> <036501d17fc3$d51357e0$7f3a07a0$@belski.net> <5E36AA30-831F-44BE-A148-8720B8E87E96@heroku.com> <94A89B0F-48BB-4DD8-A26B-3B6D2C8C2C9F@heroku.com> <7DF19331-9967-47C8-B21D-260C619BBD5E@heroku.com> <0b5101d183a1$5b38fdd0$11aaf970$@belski.net> To: Nikita Popov X-Mailer: Apple Mail (2.3112) Subject: Re: [PHP-DEV] PCRE JIT stack size limit From: dz@heroku.com (David Zuelke) On 21.03.2016, at 19:54, Nikita Popov wrote: >=20 > On Mon, Mar 21, 2016 at 7:41 PM, Anatol Belski = wrote: >> The issue I have with more increasing the stack is that - while as we = see >> till today >> the default stack size of 32K is enough in the common case, the max = of it >> will be >> reserved. So the real usage will most likely stay under 32K, but the = whole >> of max >> (say 64K now) will be unusable by anything else. >>=20 > Are you sure about that? The documentation says "The arguments are a = starting size for the stack, and a maximum size to which it is allowed = to grow." Unless I'm misunderstanding something, it should not be = allocating the maximum size right away. That's how I understood it too.