From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12416 invoked by alias); 26 Jun 2011 22:45:17 -0000 Received: (qmail 12401 invoked by uid 22791); 26 Jun 2011 22:45:14 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 26 Jun 2011 22:45:00 +0000 From: "jan.kratochvil at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/49537] New: cross-check DW_AT_name vs. demangling of linkage names X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sun, 26 Jun 2011 22:45:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg02267.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49537 Summary: cross-check DW_AT_name vs. demangling of linkage names Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: jan.kratochvil@redhat.com CC: dodji@gcc.gnu.org PR debug/49408 shows DW_AT_name "K<&S::m>" vs. demangled DW_AT_MIPS_linkage_name prefix "K<&(S::m(int))>". This was due to a bug in libiberty/cp-demangle.c. http://gcc.gnu.org/ml/gcc/2011-06/msg00308.html On Wed, Jun 22, 2011 at 10:42 AM, Jason Merrill wrote: > Well, the basic issue is that the "linkage name" is produced > by libiberty/cp-demangle.c and the DW_AT_name is produced by gcc/cp/error.c, > and they don't always agree on the same pretty-printed representation > of a C++ expression. Therefore I believe there could be compile time sanity cross-check with ICE in such cases, maybe more such bugs exist there already.