From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, 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: Mon, 26 Mar 2018 14:26:00 -0000 [thread overview]
Message-ID: <b47cf438-b948-f5d1-2901-bd3ebd6123b1@redhat.com> (raw)
In-Reply-To: <20180319212158.narawyklbdhitd6i@adacore.com>
Hi Joel,
On 03/19/2018 09:21 PM, Joel Brobecker wrote:
> On Wed, Feb 21, 2018 at 07:02:11AM +0400, Joel Brobecker wrote:
>>>> All in all, I think a better solution would be to put that information
>>>> directly in the language_defn itself, via a new "attribute".
>>>> Something like a...
>>>
>>> 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.
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".
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...
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-03-26 14:26 UTC|newest]
Thread overview: 25+ 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
[not found] ` <250976c6-6e7a-6a8e-b9f2-a57f5b92b965@redhat.com>
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 ` Pedro Alves [this message]
2018-03-27 14:02 ` PING^2: [RFA/RFC] fix PR gdb/22670 (pb looking up some symbols when they have a linkage name) Joel Brobecker
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=b47cf438-b948-f5d1-2901-bd3ebd6123b1@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.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