Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13152 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83027 invoked by uid 1010); 4 Oct 2004 19:18:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 83000 invoked from network); 4 Oct 2004 19:18:52 -0000 Received: from unknown (HELO mproxy.gmail.com) (64.233.170.193) by pb1.pair.com with SMTP; 4 Oct 2004 19:18:52 -0000 Received: by mproxy.gmail.com with SMTP id 78so506828rnl for ; Mon, 04 Oct 2004 12:18:52 -0700 (PDT) Received: by 10.38.126.4 with SMTP id y4mr2973394rnc; Mon, 04 Oct 2004 12:18:47 -0700 (PDT) Received: by 10.38.75.12 with HTTP; Mon, 4 Oct 2004 12:18:47 -0700 (PDT) Message-ID: <24e5f3b7041004121810f59641@mail.gmail.com> Date: Mon, 4 Oct 2004 12:18:47 -0700 Reply-To: sterling@apache.org To: Ilia Alshanetsky Cc: Sebastian Bergmann , internals@lists.php.net In-Reply-To: <41619EE0.70307@prohost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41619EE0.70307@prohost.org> Subject: Re: [PHP-DEV] GCC/CFLAGS Benchmark for HEAD and PHP_5_0 From: sterling.hughes@gmail.com (Sterling Hughes) On Mon, 04 Oct 2004 15:05:04 -0400, Ilia Alshanetsky wrote: > Very interesting numbers, I'd like to second Marcus' request for a 4.3 > benchmark. > > I was somewhat surprised by O2 and O1 being slower then Os, while O3 in > some cases may end over optimizing which would it explain it's poor > showing. However, it could be that it makes simple situations slower, > while more complex operations that are generally more CPU intensive will > in fact become faster. If you don't mind, could you please all include > data for "time make test" as it seems to cover a much greater quantity > of code. > Thies and I found the same thing when we did our patch. It relates to the size of the executor loop that is generated, if you have too much inlining you end up blowing your instruction cache. -Sterling