From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 327E5385842C; Thu, 9 Feb 2023 20:54:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 327E5385842C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675976066; bh=EZMok4/pkaEGKwNuzzCC87QhXA0SD6YE6xmkyVn5G5s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kv7vu/sKpILATxfDa3G8I/bWfA2ZNTmHpQPgp3hFxLBTNIJ2U/RPmSHXY6U7a/l5H lemTe0+vvS+vanKqE9gRXzGPQra22HVKLQfsDrKZ5jsGaoQqbw0VlrrfN9YoNmtRM5 P+xAV/U7/vogZ6sclif0OEFUPmtfHg6x3tqb17FE= From: "rimvydas.jas at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108705] [13 Regression] Unexpected CPU time usage with LTO in ranger propagation Date: Thu, 09 Feb 2023 20:54:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rimvydas.jas at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108705 --- Comment #7 from Rimvydas (RJ) --- The original cases have over 65 long call cascades that take different small arrays to be packed. Because of geometric time growth for every next repea= ted call, the -flto -O2 is unusable in these specific cases. I think I found a workaround after investigating f951 internals to add supp= ort for NOINLINE attribute in form of: !GCC$ ATTRIBUTES noinline :: foo It works with LTO and might be useful for other issues. I'll post a patch = with feature request in gfortran mailing list after some testing. If the pr is not reproducible it can be closed as INVALID, since it might b= e a host software configuration specific issue.=