Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Initial pass at supporting the Go language
Date: Tue, 03 Jan 2012 20:02:00 -0000	[thread overview]
Message-ID: <4F035ECB.8060206@redhat.com> (raw)
In-Reply-To: <m3vcotncjg.fsf@fleche.redhat.com>

On 01/02/2012 11:13 AM, Tom Tromey wrote:
>>>>>> "Doug" == Doug Evans<dje@google.com>  writes:
> Doug>  +	 And if not, it should be clearly documented why not.
> Doug>  +	 OTOH, why are we demangling at all here?
> Doug>  +	 new_symbol_full assumes we return the mangled name.
> Doug>  +	 I realize things are changing in this area, I just forget how.  */
> Doug>  +      if (cu->language == language_go)
> Doug>  +	{
> Doug>  +#if 0
> Doug>  +	  demangled = cu->language_defn->la_demangle (mangled, 0);
> Doug>  +#else
> Doug>  +	  /* This is a lie, but we already lie to the caller new_symbol_full.
> Doug>  +	     This just undoes that lie until things are cleaned up.  */
> Doug>  +	  demangled = NULL;
> Doug>  +#endif
>
> I've CC'd Keith to see if he can clear this up.

I'm not sure what the question is...

This is the workaround to demangle DW_AT_[MIPS_]linkage_name if 
available instead of computing the physname. It should only be done for 
C++ and Java.

Did you want me to do something? Or ?

Keith


  parent reply	other threads:[~2012-01-03 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 21:13 Doug Evans
2011-12-29  3:50 ` Eli Zaretskii
2011-12-29  5:17 ` Joel Brobecker
2012-01-03 17:38   ` Doug Evans
2012-01-03 17:52     ` Joel Brobecker
2012-01-25 20:00   ` Doug Evans
2012-01-02 19:13 ` Tom Tromey
2012-01-03  3:20   ` Joel Brobecker
2012-01-03 18:12   ` Doug Evans
2012-01-03 19:50     ` Tom Tromey
2012-01-03 20:02   ` Keith Seitz [this message]
2015-01-20 17:34 ` golang compiler (6g) testsuite board file [Re: [RFC] Initial pass at supporting the Go language] Jan Kratochvil
2015-01-21 17:59   ` Doug Evans

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=4F035ECB.8060206@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.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