From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14328 invoked by alias); 28 Jul 2005 19:48:11 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14275 invoked by uid 22791); 28 Jul 2005 19:48:03 -0000 Received: from bethe.phy.uc.edu (HELO bethe.phy.uc.edu) (129.137.4.14) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 28 Jul 2005 19:48:03 +0000 Received: from earth.geop.uc.edu (earth.phy.uc.edu [10.44.11.234]) by bethe.phy.uc.edu (8.12.11/8.12.11) with ESMTP id j6SJm0Wr030103; Thu, 28 Jul 2005 15:48:00 -0400 Received: from earth.phy.uc.edu (localhost.localdomain [127.0.0.1]) by earth.geop.uc.edu (8.12.11/8.9.3) with ESMTP id j6SJlxZb015942; Thu, 28 Jul 2005 15:47:59 -0400 Received: (from pinskia@localhost) by earth.phy.uc.edu (8.12.11/8.12.11/Submit) id j6SJlxcX015941; Thu, 28 Jul 2005 15:47:59 -0400 From: Andrew Pinski Message-Id: <200507281947.j6SJlxcX015941@earth.phy.uc.edu> Subject: Re: Middle-end and optimization regressions: what should we do? To: fxcoudert@gmail.com Date: Thu, 28 Jul 2005 19:48:00 -0000 Cc: fortran@gcc.gnu.org (fortran@gcc.gnu.org), gcc@gcc.gnu.org In-Reply-To: <19c433eb0507281026355950aa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: -100 () USER_IN_WHITELIST X-SW-Source: 2005-07/txt/msg01186.txt.bz2 > > Hi all, > > PR 22619 and PR 22509 are two examples of recent 4.1 regressions that > showed up in gfortran, due to middle-end or optimization bugs (only > happen at -O3). Since these are regressions, they should be treated > before a long time passes, but since both source codes are Fortran, I > guess people don't (and won't) want to look at them. > > How can we help here? Is there a way to make gfortran output a > complete GIMPLE tree, that could be used for middle-end hackers to > determine where the problem is? Or are we doomed to a dichotomy to > know which patch caused these regressions? > > FX > > PS: PR 22619 appeared somewhere between 20050716 and 20050717, so > patches that could possible have messed up are: Patch which exposed it: > 2005-07-16 Danny Berlin > Kenneth Zadeck Kenny's patch exposed the latent bug. I attached a testcase to RR 22619 showing that it is a regression from 3.2.3 and it fails in 3.3 and up. Kenny's patch changes a static variable to a static const variable which gets "inlined". > PR 22509 appeared between 20050713 and 20050714, so possible guilty patches are: this was caused exposed by: 2005-07-12 Zdenek Dvorak PR rtl-optimization/20376 * toplev.c (process_options): Enable -fweb and -frename-registers when unrolling. * doc/invoke.texi: Update the information about when -fweb and -frename-registers are enabled. Thanks, Andrew Pinski