From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17755 invoked by alias); 9 May 2010 16:10:41 -0000 Received: (qmail 17654 invoked by uid 48); 9 May 2010 16:10:24 -0000 Date: Sun, 09 May 2010 16:10:00 -0000 Message-ID: <20100509161024.17653.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/msg00877.txt.bz2 ------- Comment #2 from howarth at nitro dot med dot uc dot edu 2010-05-09 16:10 ------- It appears that r159202 (for gcc trunk) and r159203 (for gcc-4_5-branch) has escalated this problem by defaulting some chipsets to the core2 tuning. PR34501 should be bumped to a P1 for both gcc trunk and gcc-4_5-branch to make sure it gets fixed before the next releases. Otherwise users of Nehalem, Westmere, Penryn and Merom class processors will find their default code generation pessimized. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34501