public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jyasskin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44641]  New: Generated constructors and destructors get wrong debug location when a typedef uses a forward declaration of the type before the definition
Date: Tue, 22 Jun 2010 22:55:00 -0000	[thread overview]
Message-ID: <bug-44641-13604@http.gcc.gnu.org/bugzilla/> (raw)

$ cat test.ii
# 1 "bad.h" 1
template <class A> struct MisplacedDbg;
# 1 "good.cc"
struct Arg;
typedef MisplacedDbg<Arg> Typedef;
template<typename T> struct Base  {
  virtual ~Base() {
  }
};
template <class A> struct MisplacedDbg : public Base<int> {
};
static MisplacedDbg<Arg> static_var;
$ g++-4.6svn -c -g test.ii
$ objdump -d -l test.o|grep -B2 'bad.h:1'
0000000000000000 <_ZN12MisplacedDbgI3ArgEC1Ev>:
MisplacedDbg():
/home/jyasskin/tmp/bad.h:1
--
0000000000000000 <_ZN12MisplacedDbgI3ArgED1Ev>:
~MisplacedDbg():
/home/jyasskin/tmp/bad.h:1
$

This causes problems for Gold's ODR violation detector.


-- 
           Summary: Generated constructors and destructors get wrong debug
                    location when a typedef uses a forward declaration of
                    the type before the definition
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jyasskin at gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44641


             reply	other threads:[~2010-06-22 22:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 22:55 jyasskin at gmail dot com [this message]
2010-07-15  0:35 ` [Bug c++/44641] " jyasskin at gmail dot com
2010-07-20  0:43 ` jyasskin at gmail dot com
2010-07-20 20:17 ` jyasskin at gcc dot gnu dot org
2010-07-20 20:22 ` jyasskin at gcc dot gnu dot org
2010-07-21 13:30 ` hjl dot tools at gmail dot com
2010-07-21 16:44 ` jyasskin at gcc dot gnu dot org
2010-07-21 16:50 ` hjl dot tools at gmail dot com
2010-07-21 18:42 ` jyasskin at gcc dot gnu dot org
2010-07-21 18:47 ` jyasskin at gcc dot gnu dot org
2010-07-21 18:48 ` jyasskin at gcc dot gnu dot org
2010-07-21 19:41 ` manu at gcc dot gnu dot org
2010-07-27  9:05 ` ubizjak at gmail dot com
2010-07-28  6:24 ` ubizjak at gmail dot com
2010-08-04 14:04 ` ubizjak at gmail dot com
2010-08-04 14:20 ` uros at gcc dot gnu dot org
2010-08-04 14:28 ` ubizjak at gmail dot com
2010-08-09  0:19 ` danglin at gcc dot gnu dot org
2010-08-09  0:35 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-10 22:14 ` danglin at gcc dot gnu dot 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-44641-13604@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).