From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>,
Tom de Vries <tdevries@suse.de>
Subject: Re: [RFC] [gdb/build] Require c++17 compiler
Date: Tue, 10 Oct 2023 11:39:20 -0600 [thread overview]
Message-ID: <87lecav0l3.fsf@tromey.com> (raw)
In-Reply-To: <87edi9xf0k.fsf@tromey.com> (Tom Tromey's message of "Thu, 05 Oct 2023 09:31:07 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> However, I do agree with Lancelot that we should do this in GDB 15.
Tom> That is, hold this patch and land it on trunk shortly after the branch
Tom> is made.
GDB 14 has branched, so I think this would be a good time to switch to
C++17 on trunk.
thanks,
Tom
next prev parent reply other threads:[~2023-10-10 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 6:54 Tom de Vries via Gdb-patches
2023-10-05 10:33 ` [PATCH RFC] " Lancelot SIX via Gdb-patches
2023-10-05 12:26 ` Andrew Burgess via Gdb-patches
2023-10-05 14:26 ` Lancelot SIX via Gdb-patches
2023-10-05 14:32 ` Simon Marchi via Gdb-patches
2023-10-05 14:55 ` Lancelot SIX via Gdb-patches
2023-10-09 14:32 ` Andrew Burgess
2023-10-05 15:55 ` Tom Tromey
2023-10-12 17:30 ` Pedro Alves
2023-10-05 15:31 ` [RFC] [gdb/build] " Tom Tromey
2023-10-10 17:39 ` Tom Tromey [this message]
2023-10-10 19:16 ` Simon Marchi
2023-10-12 17:10 ` Pedro Alves
2023-10-12 17:22 ` Pedro Alves
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=87lecav0l3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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