From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21623 invoked by alias); 30 Jan 2008 18:15:38 -0000 Received: (qmail 20802 invoked by uid 48); 30 Jan 2008 18:14:53 -0000 Date: Wed, 30 Jan 2008 18:34:00 -0000 Message-ID: <20080130181453.20801.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/17863] [4.0/4.1/4.2/4.3 Regression] performance loss (not inlining as much??) In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hubicka at gcc dot gnu dot org" 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: 2008-01/txt/msg03685.txt.bz2 ------- Comment #36 from hubicka at gcc dot gnu dot org 2008-01-30 18:14 ------- Looking at the .optimized dump, one obvious problem is that we keep a lot of pointer arithmetic that should be forward propagated: :; D.184420 = *pz; p1 = pz + 8; D.184422 = *p1; p1 = p1 + 8; D.184424 = *p1; p1 = p1 + 8; D.184426 = *p1; p1 = p1 + 8; D.184428 = *p1; p1 = p1 + 8; D.184430 = *p1; p1 = p1 + 8; D.184432 = *p1; D.184434 = *(p1 + 8); Those seems to be all just array manipulations. Honza -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17863