From: Tom Tromey <tom@tromey.com>
To: Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: apinski@marvell.com, gdb-patches@sourceware.org,
binutils@sourceware.org, Jeff Law <jeffreyalaw@gmail.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCHv2] Use toplevel configure for GMP and MPFR for gdb
Date: Wed, 16 Nov 2022 09:01:40 -0700 [thread overview]
Message-ID: <87edu2vqfv.fsf@tromey.com> (raw)
In-Reply-To: <36e23439-0429-0c02-1998-0b7a025fa64c@gmail.com> (Jeff Law via Gcc-patches's message of "Tue, 15 Nov 2022 20:59:07 -0700")
>>>>> "Jeff" == Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>> This patch uses the toplevel configure parts for GMP/MPFR for
>> gdb.
Jeff> If the GDB folks confirm they want this behavior, then the toplevel
Jeff> bits are fine.
I think we do, but my inclination is to wait until after GDB 13 branches.
CCing Joel to see what he thinks, as he handles the releases.
Tom
next prev parent reply other threads:[~2022-11-16 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:05 apinski
2022-11-16 3:59 ` Jeff Law
2022-11-16 16:01 ` Tom Tromey [this message]
2022-11-16 18:50 ` Jeff Law
2022-12-20 18:59 ` Tom Tromey
2022-12-21 3:45 ` Andrew Pinski
2022-12-21 14:56 ` Jeff Law
2022-12-21 15:03 ` Tom Tromey
2023-01-03 10:52 ` Clément Chigot
2023-01-03 11:51 ` Nick Clifton
2023-01-03 11:52 ` Andrew Pinski
2023-01-03 13:12 ` Clément Chigot
2023-08-10 12:47 ` Matthias Klose
2023-08-10 19:00 ` Arsen Arsenović
-- strict thread matches above, loose matches on Subject: below --
2022-11-10 19:03 apinski
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=87edu2vqfv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=apinski@marvell.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeffreyalaw@gmail.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).