public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PING^2: [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name)
Date: Tue, 27 Mar 2018 14:02:00 -0000	[thread overview]
Message-ID: <20180327140221.kisd66avp4slhnxp@adacore.com> (raw)
In-Reply-To: <b47cf438-b948-f5d1-2901-bd3ebd6123b1@redhat.com>

> >>> I ended up choosing this approach. lookup names is still a bit
> >>> foggy for me, so the comments I wrote and/or the name of the
> >>> new language_defn attribute might be a bit off. As always, I am
> >>> grateful for suggestions :).
> 
> I looked again at this today, and I couldn't think of a better
> option right now.  So I think you should go ahead and push this in.

Thanks, Pedro.

I re-tested the patch on x86_64-linux, and then pushed it to master.

> Note that this C++ mangled form like in "symada__cS", is not
> actually how C++ symbols are mangled nowadays.  The modern Itanium
> mangling scheme has linkage names that always start with "_Z".  In this
> case, "void symada(char, signed)" mangles as "_Z6symadaci".

Interesting.

> It's possible that we no longer need to support that older (and
> ambiguous with Ada and other languages) mangling scheme for C++, I
> don't know.  I wish Ada linkage names also had some kind of leading
> prefix, but that can't happen without an ABI break, of course...

Yeah, it's a good idea, but making that kind of change happen is
going to be tough, especially since we know there are consumers
of our debugging information that we have no control of. I'll mention
it to the compiler team, though.

Thanks Pedro.
-- 
Joel

  reply	other threads:[~2018-03-27 14:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 10:37 [RFC] regresssion(internal-error) printing subprogram argument Joel Brobecker
2017-12-14 19:02 ` Pedro Alves
2017-12-14 19:41   ` Pedro Alves
2017-12-15  9:48     ` Joel Brobecker
2017-12-15 11:02       ` Pedro Alves
2017-12-15 18:57         ` Pedro Alves
2018-01-03  4:33           ` Joel Brobecker
2018-01-04  9:48             ` Joel Brobecker
2018-01-04 12:39               ` Pedro Alves
2018-01-05 16:28             ` Pedro Alves
2018-01-16 11:54               ` Pedro Alves
2018-01-17  9:13                 ` Joel Brobecker
2018-01-26  3:51                   ` Joel Brobecker
2018-01-26 11:28                     ` Pedro Alves
2018-01-29 10:38                       ` Joel Brobecker
2018-01-29 15:33                         ` Pedro Alves
2018-01-29 15:52                           ` Joel Brobecker
2018-01-30  3:56                           ` Joel Brobecker
2018-02-05  9:57                             ` Joel Brobecker
2018-02-09  9:09                               ` [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name) (was: "Re: [RFC] regresssion(internal-error) printing subprogram argument") Joel Brobecker
2018-02-21  3:02                                 ` PING: " Joel Brobecker
2018-03-19 21:22                                   ` PING^2: " Joel Brobecker
2018-03-26 14:26                                     ` PING^2: [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name) Pedro Alves
2018-03-27 14:02                                       ` Joel Brobecker [this message]
2018-01-26  4:50                   ` [RFC] regresssion(internal-error) printing subprogram argument Joel Brobecker
2017-12-15 18:31       ` Pedro Alves
2017-12-15  7:54   ` Joel Brobecker

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=20180327140221.kisd66avp4slhnxp@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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).