From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27669 invoked by alias); 23 Jun 2013 05:25:47 -0000 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 Received: (qmail 27584 invoked by uid 48); 23 Jun 2013 05:25:37 -0000 From: "prop_design at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53957] Polyhedron 11 benchmark: MP_PROP_DESIGN twice as long as other compiler Date: Sun, 23 Jun 2013 05:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: prop_design at yahoo dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-06/txt/msg01254.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957 --- Comment #15 from Anthony Falzone --- (In reply to Dominique d'Humieres from comment #14) > Anthony, could you provide a reduced test showing the problem? Hi Dominique, About the most reduced I can think of is PROP_DESIGN_ANALYSIS. It contains the core calculations that are required to determine aircraft propeller performance. PROP_DESIGN_ANALYSIS_BENCHMARK just adds some looping options that in my mind could run in parallel. However, I don't know anything about parallel programming and when I tried some Fortran compilers with auto-parallelization non of them can pick up on the loops that too me seem obviously parallel. So what I think and what is currently feasible with auto-parallelization are not the same. In any event, I have noticed that just using O3 optimizations there is a substantial difference between Intel Fortran and gfortran. So I am just confirming what Tobias is saying here in this bug report. If PROP_DESIGN_ANALYSIS_BENCHMARK is too complex of a test case for you the only thing I can think to do is take PROP_DESIGN_ANALYSIS and strip out most of the end parts where various outputs are created. So the program would just take the inputs run the minimum calculations with the least looping possible and output pretty much nothing. It wouldn't be hard for me to do something like that if it would be of any benefit to you, I'm not sure. Also, if there is anything programming wise that you would like changed for some reason as far as Fortran syntax, I can try that too. My knowledge of Fortran is fairly basic. I tried to stick strictly to Fortran 77, since that is what I was trained in and have a lot of experience with. I don't know any other programming languages or even any other versions of Fortran such as 90/95 etc... Anthony