From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32673 invoked by alias); 9 May 2010 23:12:35 -0000 Received: (qmail 32626 invoked by uid 48); 9 May 2010 23:12:18 -0000 Date: Sun, 09 May 2010 23:12:00 -0000 Message-ID: <20100509231218.32625.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/34501] The vector cost model does not seem suited for Intel Core2Duo In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "howarth at nitro dot med dot uc dot edu" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg00940.txt.bz2 ------- Comment #5 from howarth at nitro dot med dot uc dot edu 2010-05-09 23:12 ------- Okay, my mistake. It appears that the default builds for both i386-apple-darwin* and x86_64-apple-darwin* are both leaving -mtune set at generic. However it would be a nice aim for gcc 4.6.0 to have the processor specific costs outperform the generic tuning when invoked. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34501