From: Tom Tromey <tromey@adacore.com>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Let user C-c when waiting for DWARF index finalization
Date: Wed, 14 Dec 2022 11:00:00 -0700 [thread overview]
Message-ID: <87zgbpdfxb.fsf@tromey.com> (raw)
In-Reply-To: <20221214144831.5ybamv6tpyrqsi53@ubuntu.lan> (Lancelot SIX's message of "Wed, 14 Dec 2022 14:49:28 +0000")
Lancelot> I think the "ms" suffix from chrono_literals have been introduced in
Lancelot> c++14 which we do not support.
Yeah, thanks for pointing that out. I misread the cppreference page and
thought they were C++11.
Lancelot> I guess that something like this should work for c++11:
Lancelot> std::chrono::milliseconds duration { 15 };
I've made this change.
Lancelot> I still have on my todo list to ensure that major distros do have a
Lancelot> decent and easily installable c++14 compiler so we can bump this
Lancelot> requirement in gdb, but I have not done this yet…
Yeah, that sounds nice.
Tom
next prev parent reply other threads:[~2022-12-14 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 19:27 Tom Tromey
2022-12-06 20:35 ` Simon Marchi
2022-12-14 14:49 ` Lancelot SIX
2022-12-14 18:00 ` Tom Tromey [this message]
2023-01-27 19:22 ` Tom Tromey
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=87zgbpdfxb.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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).