public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dberlin@sources.redhat.com
To: dberlin@sources.redhat.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tom.horsley@ccur.com
Subject: Re: debug/8094: bad dwarf for inlined constructors
Date: Thu, 17 Oct 2002 14:33:00 -0000 [thread overview]
Message-ID: <20021017213323.32443.qmail@sources.redhat.com> (raw)
Synopsis: bad dwarf for inlined constructors
Responsible-Changed-From-To: unassigned->dberlin
Responsible-Changed-By: dberlin
Responsible-Changed-When: Thu Oct 17 14:33:23 2002
Responsible-Changed-Why:
me
State-Changed-From-To: open->feedback
State-Changed-By: dberlin
State-Changed-When: Thu Oct 17 14:33:23 2002
State-Changed-Why:
Need a test case, for both problems, in order to debug.
Also, when you say "two separate copies of a constructor", do they have the same mangled name?
I suspect one is the in-charge constructor, and one is the not-in charge constructor, and they actually have different names.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8094
next reply other threads:[~2002-10-17 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 14:33 dberlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 21:26 neroden
2002-09-30 5:36 tom.horsley
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=20021017213323.32443.qmail@sources.redhat.com \
--to=dberlin@sources.redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=tom.horsley@ccur.com \
/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).