From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B2E143858D32; Thu, 1 Dec 2022 11:48:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B2E143858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669895286; bh=wgVhsxbte5yk8RZdp5R7mzyLFaeCkjp7DyvTKR6MEic=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UaoB6aiLPuWpzoDW7jXLb3wyEBR35pFIL70HdgAXmTN33RYrpj7YdGPrRSFqAXpXl vH4Z4bBk+GMl7cCZSSjWVro9DOQZi3bW8pLeySKPq/9itMZSc0UG6SnwPbPw9JIvyc rg8Kv8Pfsg2la6zFEggMEd6cVAQj63/IRYKw1EC4= 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 11:48:05 +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: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106746 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |vmakarov at gcc dot gnu.org --- Comment #11 from Jakub Jelinek --- I doubt the trigger is exactly CONCAT/CONCATN, I don't see those mentioned anywhere in the scheduler nor in i386 backend code related to scheduling. But the DEBUG_INSN with CONCATN in this case contains 16 MEMs, perhaps something defers some insns for later if that DEBUG_INSN is scheduled. Not very familiar with the scheduling dumps though. With: ./xgcc -B ./ -S -O2 -fsched2-use-superblocks -fcompare-debug pr106746.c -Wno-psabi --param min-nondebug-insn-uid=3D10000 -fdump-tree-all -da -fsched-verbose=3D8 I see that it is tick 24 in which insn 10148 is scheduled with -g0 and not otherwise, already in tick 21 it is: ;; 21--> 10090 xmm7=3D[dx*0x4+sp+0x8]=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20 :hsw_decodern,hsw_p23 +;; dependencies resolved: insn 10148 +;; tick updated: insn 10148 into ready ;; dependencies resolved: insn 10203 ;; tick updated: insn 10203 into ready ;; dependencies resolved: insn 10202 ;; tick updated: insn 10202 into ready ;; dependencies resolved: insn 10201 ;; tick updated: insn 10201 into ready But why, I'm not sure.=