From: Bernd Schmidt <bernds@redhat.co.uk>
To: Jeffrey A Law <law@cygnus.com>
Cc: Jason Merrill <jason@redhat.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Question about a varasm change
Date: Tue, 19 Sep 2000 08:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0009191633160.1182-100000@mahatma.cygnus.co.uk> (raw)
In-Reply-To: <19749.969291268@upchuck>
On Mon, 18 Sep 2000, Jeffrey A Law wrote:
> > * dbxout.c (dbxout_symbol_name): Use DECL_NAME rather than
> > DECL_ASSEMBLER_NAME.
> Err, don't you need to use DECL_ASSEMBLER_NAME if the decl is a
> static class member? According to the comment in that case we want the
> mangled name.
To be honest I have no idea. I just followed what Jason suggested.
Bernd
next prev parent reply other threads:[~2000-09-19 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-15 3:25 Bernd Schmidt
2000-09-18 0:24 ` Jason Merrill
2000-09-18 2:32 ` Bernd Schmidt
2000-09-18 8:34 ` Jeffrey A Law
2000-09-19 8:34 ` Bernd Schmidt [this message]
2000-09-21 14:28 ` Jason Merrill
2000-09-22 10:56 ` Jason Merrill
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=Pine.LNX.4.21.0009191633160.1182-100000@mahatma.cygnus.co.uk \
--to=bernds@redhat.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=law@cygnus.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).