From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CFE323877031; Fri, 20 Mar 2020 08:47:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CFE323877031 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584694038; bh=Pj/klrMAmhkCO4gFss0AvRwNs7Nef2LmIKeDMEl74Uw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZFJR/tO2lhRIBlriPHcNusMid7jRkf9lEAdICWMoxTVnJI5YV5m/6464ePOxGcPLq uEX7PQf2hk+e8hU1qfLRZxER/3fnEuwSv9e/741vxLlecfMKFKvrW8td6vH584KMhu FbzhEmq7KqHIHjFUZX7f5MFl0UHbZp+Rw4NyE+Qc= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94223] [10 Regression] -fcompare-debug -O0 failure on cpp1z/init-statement6.C Date: Fri, 20 Mar 2020 08:47:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2020 08:47:18 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94223 --- Comment #3 from Jakub Jelinek --- (In reply to Richard Biener from comment #2) > lhd_set_decl_assembler_name seems to only do this for local decls though > so it shouldn't matter for actual generated code but is just a > compare-debug artifact? If it matters for code-generation then yes, > a local counter should do (does it really need to be GTY?) Yes, it does that only for local decls, so partly it is a -fcompare-debug artifact (shows up e.g. in the (symbol_ref:DI "C.4.1983454")) and partly it= is observable in the symbol table. The -fcompare-debug checking comparison doesn't print DECL_UIDs, but in these cases where it is DECL_ASSEMBLER_NAME= or something that makes it into RTL it just doesn't know that it a part of the identifier was formed from a DECL_UID. As for GTY, maybe we don't need it.=