From: Kevin Buettner <kevinb@redhat.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: Fix some problems in gdb.compile
Date: Wed, 30 Nov 2022 17:17:54 -0700 [thread overview]
Message-ID: <20221130171754.3cc534e8@f35-zws-nvidia> (raw)
In-Reply-To: <20221130193531.2464972-1-tromey@adacore.com>
Hi Tom,
On Wed, 30 Nov 2022 12:35:28 -0700
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> wrote:
> I was looking into some irritating timeouts in gdb.compile and came up
> with this short series. It doesn't fix any of the underlying issues,
> but it at least makes the tests complete reasonably quickly.
Thanks for working on this problem.
I've looked at all three patches in this series. All three look good
to me.
Kevin
prev parent reply other threads:[~2022-12-01 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 19:35 Tom Tromey
2022-11-30 19:35 ` [PATCH 1/3] Remove one copy of skip_compile_feature_tests Tom Tromey
2022-11-30 19:35 ` [PATCH 2/3] Remove obsolete check from skip_compile_feature_tests Tom Tromey
2022-11-30 19:35 ` [PATCH 3/3] Avoid timeouts in gdb.compile Tom Tromey
2022-12-01 0:17 ` Kevin Buettner [this message]
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=20221130171754.3cc534e8@f35-zws-nvidia \
--to=kevinb@redhat.com \
--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).