From: Luis Machado <luis.machado@arm.com>
To: Pedro Alves <pedro@palves.net>, gdb@sourceware.org
Cc: "Zaric, Zoran (Zare)" <Zoran.Zaric@amd.com>
Subject: Re: gmp's c++ interface / mpz_class
Date: Mon, 17 Oct 2022 11:44:57 +0100 [thread overview]
Message-ID: <1bf89db8-a04c-4297-3a5f-ae8532f6d0a4@arm.com> (raw)
In-Reply-To: <e2ccd323-a876-cd0d-4ae5-6c26a78f6224@palves.net>
On 10/14/22 19:11, Pedro Alves wrote:
> Hi!
>
> Zoran and I found a potential need for an integer type with precision of 64-bit + 8-bit, in order to
> store bit offsets that can span a whole 64-bits address space. Instead of rolling our own,
> I guess it makes sense to use libgmp, since, well, we already depend on it. I see that we have:
Is uint128_t an option (at least temporarily)?
>
> /* A class to make it easier to use GMP's mpz_t values within GDB. */
>
> struct gdb_mpz
> {
>
> In gdb/gmp-utils.h. However, we need do to arithmetic on the type, and this wrapper
> type doesn't implement operator+, operator-, etc, etc. I guess we could add those,
> as wrappers around mpz_add, etc. Or use raw mpz_add, etc. directly. However, I just found
> out that GMP already has its own C++ interface:
>
> https://gmplib.org/manual/C_002b_002b-Interface-General
>
> Before we explore this further, is there an already known reason we shouldn't be using
> that interface?
>
> Pedro Alves
next prev parent reply other threads:[~2022-10-17 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 18:11 Pedro Alves
2022-10-14 20:42 ` Pedro Alves
2022-10-19 10:28 ` Florian Weimer
2022-10-17 10:44 ` Luis Machado [this message]
2022-10-17 11:29 ` Pedro Alves
2022-10-17 17:21 ` Tom Tromey
2022-10-24 13:34 ` 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=1bf89db8-a04c-4297-3a5f-ae8532f6d0a4@arm.com \
--to=luis.machado@arm.com \
--cc=Zoran.Zaric@amd.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
/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).