From: Tom Tromey <tom@tromey.com>
To: Gary Benson via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Fix gdb.base/print-file-var.exp with Clang
Date: Fri, 30 Oct 2020 12:45:27 -0600 [thread overview]
Message-ID: <87eelftuwo.fsf@tromey.com> (raw)
In-Reply-To: <1602609978-28112-3-git-send-email-gbenson@redhat.com> (Gary Benson via Gdb-patches's message of "Tue, 13 Oct 2020 18:26:18 +0100")
>>>>> "Gary" == Gary Benson via Gdb-patches <gdb-patches@sourceware.org> writes:
Gary> gdb/testsuite/ChangeLog:
Gary> * gdb.base/print-file-var.exp (test): Separate compiler and
Gary> linker options, and build using build_executable_from_specs
Gary> to accomodate this.
Looks good. Thanks.
Tom
prev parent reply other threads:[~2020-10-30 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 17:26 [PATCH 0/2] " Gary Benson
2020-10-13 17:26 ` [PATCH 1/2] Detect and report incompatible gdb_compile options Gary Benson
2020-10-23 13:04 ` Pedro Alves
2020-11-02 14:23 ` Gary Benson
2020-10-30 18:45 ` Tom Tromey
2020-10-13 17:26 ` [PATCH 2/2] Fix gdb.base/print-file-var.exp with Clang Gary Benson
2020-10-23 13:05 ` Pedro Alves
2020-11-02 14:24 ` Gary Benson
2020-10-30 18:45 ` Tom Tromey [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=87eelftuwo.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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).