Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:12899 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1288 invoked by uid 1010); 19 Sep 2004 08:02:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 1264 invoked from network); 19 Sep 2004 08:02:41 -0000 Received: from unknown (HELO mproxy.gmail.com) (64.233.170.198) by pb1.pair.com with SMTP; 19 Sep 2004 08:02:41 -0000 Received: by mproxy.gmail.com with SMTP id 79so974840rnl for ; Sun, 19 Sep 2004 01:02:41 -0700 (PDT) Received: by 10.38.163.33 with SMTP id l33mr221090rne; Sun, 19 Sep 2004 01:02:41 -0700 (PDT) Received: by 10.38.82.41 with HTTP; Sun, 19 Sep 2004 01:02:41 -0700 (PDT) Message-ID: <344de28704091901024b5e8902@mail.gmail.com> Date: Sun, 19 Sep 2004 10:02:41 +0200 Reply-To: meno.abels@adviser.com To: Rasmus Lerdorf Cc: internals@lists.php.net In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Subject: Re: [PHP-DEV] Intel icc compiler warnings From: meno.abels@gmail.com (Meno Abels) Hello, my experiences with performance and icc are, it is only faster if you use the highest optimization flags and the exact target processor flags. If you have a amd based notebook you are not in business with icc. -meno