From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11287 invoked by alias); 16 May 2010 11:17:03 -0000 Received: (qmail 11199 invoked by uid 48); 16 May 2010 11:16:40 -0000 Date: Sun, 16 May 2010 11:17:00 -0000 Message-ID: <20100516111640.11198.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/40873] -fwhole-file -fwhole-program: Wrong decls cause too much to be optimized away In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dominiq at lps dot ens dot fr" 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/msg01707.txt.bz2 ------- Comment #9 from dominiq at lps dot ens dot fr 2010-05-16 11:16 ------- > You cant' compare -fwhole-file numbers to -fwhole-program numbers. > -fwhole-file is a correctness option, w/o it the Frontend generates > an invalid representation for the middle-end. Well, from what I saw running the polyhedron tests, -fwhole-file is more than a correctness option. I think it exposes more optimization opportunities to the middle end, giving faster executable for ac, aermod, and doduc. Note that adding -flto gives also some speed up for these tests. Due to this pr one cannot test the effect of -fwhole-program on half the tests. However using it for fatigue gives a quite large speed up I do not see for the seven other tests. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40873