From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2BFD23858C5F; Tue, 12 Mar 2024 07:49:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BFD23858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710229784; bh=n6EJVf7XTSZQ+f/rxyu1F+7BCr4WLrBbU8y4fCUdnTM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nE7E2s0F8NBiUUkAxOombSEL6DvAhs8fgoqNDFm5bJVi3YuQUy5bYfznbfg4lpRWd d/vR6RsvX3m9l4yHx3Ftp7AHabX88VD84KwDhrKyqdCcMXco6+R8UeDo/nYDLUHfEN GSyK+Y5oZRgYs0e3kjlGM0O/7jMSWlPx838h13XI= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/114261] [13/14 Regression] Scheduling takes excessive time (97%) since r13-5154-g733a1b777f1 Date: Tue, 12 Mar 2024 07:49:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 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=3D114261 --- Comment #6 from Richard Biener --- Isn't the "scheduling window" limited somehow? Can we impose an upper boun= d on the number of dependences by placing a "virtual barrier" when we hit that limit? I don't know the structure of the scheduler or it's dependence analysis framework. In other places where GCC faces this usual quadraticness in dependence anal= ysis we have such limits and try to cope with it as good as we can, worst give up completely.=