From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3488F3858C3A; Wed, 13 Mar 2024 14:08:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3488F3858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710338899; bh=2tSQ3QB0XMDba1MXs1rIc1SPi0jaGUvxldyo+0/45Uw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KNfyDPfzbkFFZ419XmtOxVbm8wPvxsDYv1iSUyWFUggKGEdo7nK/cDQp8VyIuIwU/ zcF8vdWZRM9xeVJ+ph09NuijYOfq/hAkxl7NOA7xEwBnWvaeQxKwHJ536S3sb8TJyK cGcd2GaNAm3I1zDAxydcZQ2TAacQtap+Vi+DUK/k= 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: Wed, 13 Mar 2024 14:08:17 +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 #9 from Richard Biener --- As far as I understand the testcase is from fuzzing so not "real", so I thi= nk this proposed "fix" isn't necessary (and it's not a real fix, adding a setjmp call at the end of the function will restore it).=