From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18863 invoked by alias); 23 Feb 2007 13:17:06 -0000 Received: (qmail 18855 invoked by uid 22791); 23 Feb 2007 13:17:05 -0000 X-Spam-Check-By: sourceware.org Received: from mail-in-05.arcor-online.net (HELO mail-in-05.arcor-online.net) (151.189.21.45) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 23 Feb 2007 13:16:55 +0000 Received: from mail-in-07-z2.arcor-online.net (mail-in-07-z2.arcor-online.net [151.189.8.19]) by mail-in-05.arcor-online.net (Postfix) with ESMTP id 8C41437A523; Fri, 23 Feb 2007 14:16:52 +0100 (CET) Received: from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net [151.189.21.42]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id 74DCC2C6E4C; Fri, 23 Feb 2007 14:16:52 +0100 (CET) Received: from [192.168.1.33] (dslb-084-056-203-128.pools.arcor-ip.net [84.56.203.128]) by mail-in-02.arcor-online.net (Postfix) with ESMTP id 040AA2D8B77; Fri, 23 Feb 2007 14:16:51 +0100 (CET) In-Reply-To: <314660.44405.qm@web23401.mail.ird.yahoo.com> References: <314660.44405.qm@web23401.mail.ird.yahoo.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: gcc-help From: Segher Boessenkool Subject: Re: Best mcpu option for amcc440 with fpu ? Date: Fri, 23 Feb 2007 13:27:00 -0000 To: Patrice Bouchand X-Mailer: Apple Mail (2.623) X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-02/txt/msg00306.txt.bz2 > I'm having trouble trying to find the best > compiling > option for amcc440 with fpu. I'm using a genuine > fedora core 6 ppc distro (gcc4.1.1). It seems that > using mcpu=440 gives better results than -mcpu=440fp, > even with floating point code ? What could be wrong on > > my platform to give such a result ? Dunno. You need to hunt down more details first: -- Run a profiler (oprofile, gprof) to pinpoint one specific (preferably smallish) piece of code that has a huge slowdown; -- Look at the generated assembler code for that routine to see what's up; -- Try to figure out why that happened, or report back here. Segher