From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 96068385AC29; Thu, 1 Dec 2022 14:42:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 96068385AC29 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669905749; bh=fUwpQoKlI5P3p9v/hTwq6ujhp7eVEwCqJNngmgjOW9c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ymyh/YJ6KsPciw3GABvGy0CAbUlVTfTqIMJqTVIFqGNAaEFE7qHIww06+8+/6UVQU NMJVwohd+2E7sp5t1D5EARXe6GfqiuSu82lKwFoQG4pf4oYAXvysbviGPc8Q2nQ7GP ZfboXP/bMHd0PUpmBxWlOgdVlKUAZfGTbllH48Po= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/106746] [13 Regression] '-fcompare-debug' failure (length) with -O2 -fsched2-use-superblocks since r13-2041-g6624ad73064de241 Date: Thu, 01 Dec 2022 14:42:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: compare-debug-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 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=3D106746 --- Comment #14 from Jakub Jelinek --- (In reply to Segher Boessenkool from comment #13) > DEBUG_INSNs should never influence any scheduling decisions, or any other > decisions that influence what machine code we generate. Well, with the exception of scheduling decisions for the DEBUG_INSNs themse= lves (where exactly to place them). haifa-sched.cc is full of various DEBUG_INSN related checks, in some cases DEBUG_INSNs are ignored, in other places they are taken into account, ... And in the end, most of the time it works fine for -fcompare-debug checks; = it doesn't for this testcase, so that needs to be understood why and fixed.=