From: Tom Tromey <tom@tromey.com>
To: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Lancelot SIX <lsix@lancelotsix.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] gdb/amdgpu: provide dummy implementation of gdbarch_return_value_as_value
Date: Tue, 07 Mar 2023 13:44:14 -0700 [thread overview]
Message-ID: <87a60oqokh.fsf@tromey.com> (raw)
In-Reply-To: <20230307203309.i75k6nlj4bh3axc6@ubuntu.lan> (Lancelot SIX via Gdb-patches's message of "Tue, 7 Mar 2023 20:33:09 +0000")
Lancelot> We have discussed this a bit off-list, and our understanding is that the
Lancelot> gdbarch hook has to implement the standard ABI.
Yeah, agreed.
Lancelot> I am not sure how we would model the ticket you linked above. Could the
Lancelot> arch implement a "rust on $ARCH" ABI in the gdbarch hook by inspecting
Lancelot> the language of the CU the function belongs to? This would need the
Lancelot> custum ABI to be stable, and I have no idea if this is the case for
Lancelot> rust.
It's not, so it would be premature for gdb to do anything like that.
The Rust proposal is to extend DWARF (in some unspecified way) so that
the compiler can describe the ABI in use. If that ever happens I guess
we can implement it.
Tom
prev parent reply other threads:[~2023-03-07 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 21:46 Simon Marchi
2023-03-07 10:45 ` Lancelot SIX
2023-03-07 14:47 ` Simon Marchi
2023-03-07 19:12 ` Lancelot SIX
2023-03-07 19:20 ` Tom Tromey
2023-03-07 20:32 ` Simon Marchi
2023-03-07 20:44 ` Tom Tromey
2023-03-07 20:33 ` Lancelot SIX
2023-03-07 20:44 ` Tom Tromey [this message]
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=87a60oqokh.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simon.marchi@polymtl.ca \
/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).