public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/67664] New: [6 Regression] Duplicate AT_const_value attributes in some c++ cases. Date: Mon, 21 Sep 2015 09:07:00 -0000 [thread overview] Message-ID: <bug-67664-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67664 Bug ID: 67664 Summary: [6 Regression] Duplicate AT_const_value attributes in some c++ cases. Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: iains at gcc dot gnu.org Target Milestone: --- [AFAICT] between 227779 and 227800 a change was introduced that causes multiple instances of AT_const_value to be inserted in some DIEs. This is picked up by Darwin's dsymutil and results in wide-spread fails in the libstdc++ test suite for both m32 and m64. The duplicate is not detected by binutils ld, but appears to be present on a current build of x86_64-linux-gnu. testcase libstdc++/17_intro/freestanding.cc: linux (r227958): <2><398>: Abbrev Number: 25 (DW_TAG_structure_type) <399> DW_AT_name : (indirect string, offset: 0x7be): numeric_limits<long int> <39d> DW_AT_byte_size : 1 <39e> DW_AT_decl_file : 8 <39f> DW_AT_decl_line : 1132 <3a1> DW_AT_sibling : <0x578> <3><3a5>: Abbrev Number: 26 (DW_TAG_member) <3a6> DW_AT_name : (indirect string, offset: 0x75f): is_specialized <3aa> DW_AT_decl_file : 8 <3ab> DW_AT_decl_line : 1134 <3ad> DW_AT_type : <0xc81> <3b1> DW_AT_external : 1 <3b1> DW_AT_declaration : 1 <3b1> DW_AT_const_value : 1 <3b2> DW_AT_const_value : 1 <3><3b3>: Abbrev Number: 26 (DW_TAG_member) <3b4> DW_AT_name : (indirect string, offset: 0x503): digits <3b8> DW_AT_decl_file : 8 <3b9> DW_AT_decl_line : 1147 <3bb> DW_AT_type : <0x8dd> <3bf> DW_AT_external : 1 <3bf> DW_AT_declaration : 1 <3bf> DW_AT_const_value : 63 <3c0> DW_AT_const_value : 63 <3><3c1>: Abbrev Number: 26 (DW_TAG_member) ====== Darwin (r227952): 0x000003ff: TAG_structure_type [14] * AT_name( "numeric_limits<long int>" ) AT_byte_size( 0x01 ) AT_decl_file( "/Volumes/Data0/gcc-trunk/libstdc++-v3/include/std/limits" ) AT_decl_line( 1132 ) AT_sibling( {0x00000835} ) 0x00000421: TAG_member [15] AT_name( "is_specialized" ) AT_decl_file( "/Volumes/Data0/gcc-trunk/libstdc++-v3/include/std/limits" ) AT_decl_line( 1134 ) AT_type( {0x000003c8} ( const bool ) ) AT_external( 0x01 ) AT_declaration( 0x01 ) AT_const_value( 0x01 ) AT_const_value( 0x01 ) 0x0000043c: TAG_member [15] AT_name( "digits" ) AT_decl_file( "/Volumes/Data0/gcc-trunk/libstdc++-v3/include/std/limits" ) AT_decl_line( 1147 ) AT_type( {0x000003cd} ( const int ) ) AT_external( 0x01 ) AT_declaration( 0x01 ) AT_const_value( 0x1f ) AT_const_value( 0x1f )
next reply other threads:[~2015-09-21 9:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-21 9:07 iains at gcc dot gnu.org [this message] 2015-09-21 9:24 ` [Bug debug/67664] " rguenth at gcc dot gnu.org 2015-09-21 9:33 ` rguenth at gcc dot gnu.org 2015-09-21 9:46 ` rguenth at gcc dot gnu.org 2015-09-21 14:03 ` rguenth at gcc dot gnu.org 2015-09-21 14:05 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-67664-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).