From: Andrew Pinski via Gdb <gdb@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: lijiang <lijiang@redhat.com>, gdb@sourceware.org
Subject: Re: About gmp and mpfr dependencies for gdb building
Date: Thu, 13 Mar 2025 13:37:07 -0700 [thread overview]
Message-ID: <CA+=Sn1msugJKdp0FMqXXocud3+_OPzbCJNDbD_G6BKvRJFMGUw@mail.gmail.com> (raw)
In-Reply-To: <87wmcsvfoa.fsf@tromey.com>
On Thu, Mar 13, 2025 at 1:31 PM Tom Tromey <tom@tromey.com> wrote:
>
> > For the gmp and mpfr dependency libs, is it possible to provide an
> > option to enable/disable the gmp and mpfr instead of forcely enabling
> > them when building gdb?
>
> Not currently.
>
> You could probably try to implement it. One way might be to replace the
> use of GMP with a custom wide-int implementation; or with (assuming
> IIRC) the slower single-header GMP implementation. Not sure about MPFR.
>
> Probably use of wide-int in gdb is just going to grow due to 128-bit
> ints becoming more common.
Well and BitInt increases the wide-int even further past the 128bit
wide length too.
GCC has its own wide-int implementation which might be useful to pull
into GDB if needed. It is used for BitInt and wide integer too.
MPFR might be hard to replace for floating point types are hard to
emulate exactly.
GCC does have some code to do some but most of the folding (except for
simple things) are handled via MPFR also.
Thanks,
Andrew Pinski
>
> thanks,
> Tom
next prev parent reply other threads:[~2025-03-13 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 8:14 lijiang via Gdb
2025-03-13 8:32 ` Iru Cai via Gdb
2025-03-13 20:28 ` Tom Tromey
2025-03-13 20:37 ` Andrew Pinski via Gdb [this message]
2025-03-13 22:09 ` Tom Tromey
2025-03-17 8:29 ` lijiang via Gdb
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='CA+=Sn1msugJKdp0FMqXXocud3+_OPzbCJNDbD_G6BKvRJFMGUw@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=lijiang@redhat.com \
--cc=pinskia@gmail.com \
--cc=tom@tromey.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