From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Rewrite gdb_mpz::operator==
Date: Wed, 19 Apr 2023 12:23:18 -0400 [thread overview]
Message-ID: <119e1750-83c2-9e9f-a60a-3c14b2d6c09a@simark.ca> (raw)
In-Reply-To: <20230419150931.2047832-1-tromey@adacore.com>
On 4/19/23 11:09, Tom Tromey via Gdb-patches wrote:
> Simon pointed out that the recent changes to gdb_mpz caused a build
> failure on macOS. It turns out to be somewhat difficult to overload a
For some reason, just macOS on amd64, not arm64.
> method in a way that will work "naturally" for all integer types;
> especially in a case like gdb_mpz::operator==, where it's desirable to
> special case all integer types that are no wider than 'long'.
>
> After a false start, I came up with this patch, which seems to work.
> It applies the desirable GMP special cases directly in the body,
> rather than via overloads.
> ---
> gdb/gmp-utils.h | 38 ++++++++++++++------------------------
> 1 file changed, 14 insertions(+), 24 deletions(-)
>
> diff --git a/gdb/gmp-utils.h b/gdb/gmp-utils.h
> index d05c11ecbe4..3586d01b0f9 100644
> --- a/gdb/gmp-utils.h
> +++ b/gdb/gmp-utils.h
> @@ -323,31 +323,21 @@ struct gdb_mpz
> return mpz_cmp_si (m_val, other) < 0;
> }
>
> - bool operator== (int other) const
> - {
> - return mpz_cmp_si (m_val, other) == 0;
> - }
> -
> - bool operator== (long other) const
> - {
> - return mpz_cmp_si (m_val, other) == 0;
> - }
> -
> - bool operator== (unsigned long other) const
> - {
> - return mpz_cmp_ui (m_val, other) == 0;
> - }
> -
> template<typename T,
> - typename = gdb::Requires<
> - gdb::And<std::is_integral<T>,
> - std::integral_constant<bool,
> - (sizeof (T) > sizeof (long))>>
> - >
> - >
> - bool operator== (T src)
> - {
> - return *this == gdb_mpz (src);
> + typename = gdb::Requires<std::is_integral<T>>>
> + bool operator== (T other) const
> + {
> + if (std::is_signed<T>::value)
> + {
> + if (other == (T) (long) other)
It's a bit hard to understand what the intent is, if you don't know the
problematic already. Could you add a comment explaining that?
Also, wouldn't it work to compare size? Like:
if (sizeof (T) <= sizeof (long))
Simon
next prev parent reply other threads:[~2023-04-19 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 15:09 Tom Tromey
2023-04-19 16:23 ` Simon Marchi [this message]
2023-04-21 13:00 ` Tom Tromey
2023-04-21 13:13 ` Simon Marchi
2023-04-21 15:02 ` Tom Tromey
2023-04-24 16:31 ` Tom Tromey
2023-04-25 18:55 ` Simon Marchi
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=119e1750-83c2-9e9f-a60a-3c14b2d6c09a@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).