Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103041 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61151 invoked from network); 4 Aug 2018 20:46:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2018 20:46:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=mail@majkl578.cz; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mail@majkl578.cz; sender-id=pass Received-SPF: pass (pb1.pair.com: domain majkl578.cz designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: mail@majkl578.cz X-Host-Fingerprint: 74.125.82.53 mail-wm0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:38225] helo=mail-wm0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/D2-28158-CA0166B5 for ; Sat, 04 Aug 2018 16:46:37 -0400 Received: by mail-wm0-f53.google.com with SMTP id t25-v6so10038572wmi.3 for ; Sat, 04 Aug 2018 13:46:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=majkl578.cz; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=Ukd4wVTLUB3dkNbXYV5KbgmMIM98dBjZDlpY9wqyA4g=; b=a0SeSU8cvixE6xJs8QulzXlKgoSNsJfwXA8eDP5wwUxV0SCtXzPjdDKdxDoihL8rWz bUvsenkt1LFaYkCBBgB0U//jTXQphG5EIILd7jt5tKM89N/qSArz0suVIcjSmRUlbsQ/ bapj7a3Sxrua4rWXtH9kNZksreoVvNs6jHmTBkufGalp4/CEYP4jbuVyyRptpciwtnBo jZjrrs2PREa+/Je62T29WZBtYuI2jn2ZDgJx4jew1hqTafTJIobbo0BuL7PXe6ki1VFH o27Vpre7hkK05VjhPCXrT8qQvhvJsyVLPFEgQmAxKx0szU/EMZrhfOgP37aEj8ZnUjEX XF1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Ukd4wVTLUB3dkNbXYV5KbgmMIM98dBjZDlpY9wqyA4g=; b=KJMNKjkvFfaxtfVFFsHedMWk5U9F3qIyA7h1pWn6/GDP8Qq+ouk8cQtN5dBFmgULJx 7isLoyHYyUS7B10CEpuq1CH6vr1V7uB0qPXqKXyxmuV63QiL7CItFP5hI0mqyg01gBJi n8IZDWIGu9ig69PjPYmVRZQlGXznCzxEtsfIdetW5+g7vb0PoM8C9rqieB84cCEy5mHs 0zs/+/9HwJNVzhEbj0b69SAGnvJSb4RaA9H6iInWsZH0mQuk4FgmEAlbGhs/o1xVWicG 0RoE1X2ENS8pzmE2qsOIAXK3nocBhp/H8/qd7yPGcMmvoHhaRMh/a7CDv57cE1p+8F8Q 1AdQ== X-Gm-Message-State: AOUpUlFg45MLDHAL6dMxyNj37VsUTA8Pju5b2xr/UBu3YlCKZqDtuOiY dS57jkXK9vaN07AZkzgj8zhgBR07hGtZ/SkZIgLpqAnaj5WXRQ== X-Google-Smtp-Source: AAOMgpdTN3f+2rMjiMufHRPeUB6Dg23O74Z2fIDalYJegjAgjNeTLHFfAjd07rectxkxdMkyzfQmptI4Y2Ptb83L+hY= X-Received: by 2002:a1c:357:: with SMTP id 84-v6mr7732770wmd.8.1533415593929; Sat, 04 Aug 2018 13:46:33 -0700 (PDT) MIME-Version: 1.0 Sender: mail@majkl578.cz Received: by 2002:adf:e38e:0:0:0:0:0 with HTTP; Sat, 4 Aug 2018 13:46:13 -0700 (PDT) X-Originating-IP: [2a00:1028:9190:d232:565:a6e3:265:faf6] Date: Sat, 4 Aug 2018 22:46:13 +0200 X-Google-Sender-Auth: 8ZPtLmMfx8vcPHZWhLABOJJEmoA Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000c509e70572a2230a" Subject: GCC -foptimize-strlen and bug #76510 From: php.net@majkl578.cz (Michael Moravec) --000000000000c509e70572a2230a Content-Type: text/plain; charset="UTF-8" Hi, yesterday I was digging into the bug #76510: https://bugs.php.net/bug.php?id=76510 A strange PHAR- and streams-related issue that only happens for some users/binaries. I was able to trace it down to a GCC optimization "optimize-strlen". Here's when the bug does and does not reproduce: gcc-8 with -O0 works gcc-8 with -O1 works gcc-8 with -O2 does not work gcc-8 with -O3 does not work gcc-8 with -Og works gcc-8 with -Os works With some further testing, I was able to find a workaround: -O2 -fno-optimize-strlen I bisected this issue to the commit 513b0093c2b480bb752fb354012f42c446769486: Refactor php_url struct to save memory dup in common cases https://github.com/php/php-src/commit/513b0093c2b480bb752fb354012f42c446769486 (bisect log is in the bug report) To confirm: git checkout 513b0093c2b480bb752fb354012f42c446769486 + gcc-8 + -O2: Fatal error git checkout 513b0093c2b480bb752fb354012f42c446769486^ + gcc-8 + -O2: works Unfortunately this is where my journey ends - my C/GCC knowledge is not sufficient enough to analyse this further. I'd like to ask someone to take over from here so we can see this issue fixed in the next 7.3 pre-release. Thank you, M. --000000000000c509e70572a2230a--