From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A7D2B386F02B; Tue, 21 Apr 2020 16:00:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A7D2B386F02B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587484845; bh=/eyoHAUutcK7zZqSG3RNgt4+qg2twgvdBvCJ4z4eyfc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PeSRKqcYuKtPAtOUXIvvDds20ulUdTtrbMPsVDz4d07fGH1KoWW+sbx/AOHAipVRY w/8Npfxwv/k4A3gDBWvMVGdZ2e5sXFE8XwtuVUNbqGftL/3ag2IQisZFgyqYmnQuZw 4n+K0EYHqCJdq1+jOQwwvNQCd+TZKXjjvY0xICzs= From: "seurer at linux dot vnet.ibm.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/91512] [10 Regression] Fortran compile time regression. Date: Tue, 21 Apr 2020 16:00:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at linux dot vnet.ibm.com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2020 16:00:45 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D91512 Bill Seurer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seurer at linux dot vnet.i= bm.com --- Comment #25 from Bill Seurer --- This is affecting us on powerpc64 as well. It takes twice as long to build= the spec2017 test cases with most of the difference in a few of the fortran compilations which take 30 times or more longer. I tried the new option bu= t it seems to have no effect. Some quick comparison timings: compiling module_first_rk_step_part1.fppized.f90 (part of 521.wrf_r) r10-484: 0m17, 0m14 r10-485: 9m19, 9m17 r10-7837 (current-ish trunk): 9m57, 10m3 r10-7837 with -finline-arg-packing: 9m58, 9m59 Compiling all of spec2017 r10-484: 34m8=20 r10-485: 65m1=20=20 r10-7837: 63m47=20=20 r10-7837 w. option: 65m36=