From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: Minor cleanup in some gdb.arch/* tests
Date: Fri, 23 Mar 2018 10:13:00 -0000 [thread overview]
Message-ID: <b76de8f9-c17e-e178-82ce-c8f805c96527@redhat.com> (raw)
In-Reply-To: <20180322225911.GA13407@embecosm.com>
On 03/22/2018 10:59 PM, Andrew Burgess wrote:
> I've updated inline with your suggestion. I've also converted the
> uses of gdb_compile to prepare_for_testing as I believe in these cases
> the outcome is the same. I compared the compile commands in the log
> file, prepare_for_testing does split out the object file step into a
> separate command, but otherwise I think the command are identical.
>
> Anyway, how's this?
Great, OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-03-23 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 12:57 [PATCH 0/2] Test fix in " Andrew Burgess
2018-03-22 12:57 ` [PATCH 1/2] gdb: Minor cleanup in some " Andrew Burgess
2018-03-22 13:51 ` Pedro Alves
2018-03-22 22:59 ` Andrew Burgess
2018-03-23 10:13 ` Pedro Alves [this message]
2018-03-22 12:57 ` [PATCH 2/2] gdb: Fix testsuite issue in gdb.arch/amd64-disp-step-avx.exp Andrew Burgess
2018-03-22 13:44 ` Pedro Alves
2018-03-22 23:01 ` Andrew Burgess
2018-03-23 10:13 ` 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=b76de8f9-c17e-e178-82ce-c8f805c96527@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.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).