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



------- Comment #6 from jyasskin at gcc dot gnu dot org  2010-07-21 16:44 -------
Is the problem a bad mangling or bad line numbers? In a built tree, could you
run:
  $objdir/gcc/cc1plus -g -dA
$srcdir/gcc/testsuite/g++.dg/debug/dwarf2/pr44641.C -o pr44641.s
and send me or attach pr44641.s?

Feel free to xfail this in the mean time, or if you send me your triple I'll do
it, so that it's not polluting your test results.


-- 

jyasskin at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl dot tools at gmail dot
                   |                            |com
         AssignedTo|unassigned at gcc dot gnu   |jyasskin at gcc dot gnu dot
                   |dot org                     |org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-21 16:44:41
               date|                            |


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


  parent reply	other threads:[~2010-07-21 16:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 22:55 [Bug c++/44641] New: " jyasskin at gmail dot com
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 [this message]
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
     [not found] <bug-44641-4@http.gcc.gnu.org/bugzilla/>
2010-12-09 14:43 ` danglin at gcc dot gnu.org
2010-12-09 14:52 ` danglin at gcc dot gnu.org
2011-01-21 12:36 ` ro at gcc dot gnu.org
2011-01-21 12:38 ` ro at gcc dot gnu.org
2011-03-25 20:01 ` jakub at gcc dot gnu.org
2011-04-28 16:34 ` rguenth at gcc dot gnu.org
2011-12-08 20:03 ` pinskia at gcc dot gnu.org
2011-12-08 20:18 ` pinskia at gcc dot gnu.org
2011-12-08 20:37 ` pinskia at gcc dot gnu.org
2013-11-08 10:56 ` paolo.carlini at oracle dot com

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=20100721164444.3746.qmail@sourceware.org \
    --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).