From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8159 invoked by alias); 8 Jun 2010 13:54:51 -0000 Received: (qmail 8124 invoked by uid 48); 8 Jun 2010 13:54:39 -0000 Date: Tue, 08 Jun 2010 13:54:00 -0000 Message-ID: <20100608135439.8123.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/44423] [4.5/4.6 Regression] Massive performance regression in SSE code due to SRA In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "martin at mpa-garching dot mpg dot de" 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-06/txt/msg00887.txt.bz2 ------- Comment #5 from martin at mpa-garching dot mpg dot de 2010-06-08 13:54 ------- (In reply to comment #2) > We have (4.4): > > : > va.f[0] = a->r; > va.f[1] = a->g; > va.f[2] = a->b; > va.f[3] = 0.0; > pretmp.40 = va.v; > ivtmp.61 = 0; [...] Could you please tell me the compiler flag(s) needed to produce this kind of information? That seems much more useful for debugging and chasing performance bottlenecks than assembler dumps... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44423