public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dehao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/67162] New: g2 generates incorrect decl_line
Date: Sun, 09 Aug 2015 06:17:00 -0000	[thread overview]
Message-ID: <bug-67162-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67162

            Bug ID: 67162
           Summary: g2 generates incorrect decl_line
           Product: gcc
           Version: 6.0
            Status: RESOLVED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dehao at gcc dot gnu.org
  Target Milestone: ---
            Status: RESOLVED
        Resolution: FIXED

#g++ -c -o ValueStore.o   -O2 -g1        ValueStore.ii
#objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf
    <615>   DW_AT_name        : (indirect string, offset: 0x490): isDuplicateOf
    <619>   DW_AT_decl_file   : 11
    <61a>   DW_AT_decl_line   : 297

#g++ -c -o ValueStore.o   -O2 -g2        ValueStore.ii
#objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf
    <5114>   DW_AT_name        : (indirect string, offset: 0x563d):
isDuplicateOf
    <5118>   DW_AT_decl_file   : 51
    <5119>   DW_AT_decl_line   : 150

g1 generates correct decl_line, but g2 generates incorrect decl_line (150 is
the decl_line for another function: addValue)

--- Comment #1 from dehao at gcc dot gnu.org ---
dup entry


                 reply	other threads:[~2015-08-09  6:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-67162-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: link
Be 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).