public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>, gdb@sourceware.org
Cc: "Zaric, Zoran (Zare)" <Zoran.Zaric@amd.com>
Subject: Re: gmp's c++ interface / mpz_class
Date: Mon, 17 Oct 2022 12:29:51 +0100	[thread overview]
Message-ID: <11c78d03-0823-32c6-1d66-6f814bef7057@palves.net> (raw)
In-Reply-To: <1bf89db8-a04c-4297-3a5f-ae8532f6d0a4@arm.com>

On 2022-10-17 11:44 a.m., Luis Machado wrote:
> 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)?

That is not portable, unfortunately.  It doesn't exist in all compilers, and/or all architectures.

So it's useful to prototype things, but it's not something we can use, because we need this in
core code (DWARF expression evaluation).

We may end up with something like a typedef that maps to int128_t when available,
and to a C++ class emulation when not available, though.

  reply	other threads:[~2022-10-17 11:29 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
2022-10-17 11:29   ` Pedro Alves [this message]
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=11c78d03-0823-32c6-1d66-6f814bef7057@palves.net \
    --to=pedro@palves.net \
    --cc=Zoran.Zaric@amd.com \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@arm.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).