From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Tweak gdb.trace/tfile.c for thumb mode
Date: Tue, 15 Jul 2014 14:38:00 -0000 [thread overview]
Message-ID: <53C537A1.9080802@redhat.com> (raw)
In-Reply-To: <53C53319.7090001@codesourcery.com>
Thanks Yao,
On 07/15/2014 02:56 PM, Yao Qi wrote:
> Make sure I understand you correctly, you fixed warnings on mingw32 but
> didn't run the test on mingw32, did you?
Correct, I did not run the test on mingw32, nor on Thumb, as I don't
have setups for that.
As it passes cleanly on F20, both -m64 and -m32, and now builds without
warnings on mingw32, so I'm positive I can't have broken things
that much. :-)
Do you want to test it first, or shall we push it in now, and it gets
coverage next time it percolates to your setups through mainline?
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2014-07-15 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 3:52 Yao Qi
2014-07-09 11:55 ` Yao Qi
2014-07-09 14:52 ` Pedro Alves
2014-07-10 1:30 ` Yao Qi
2014-07-15 13:20 ` Pedro Alves
2014-07-15 14:16 ` Yao Qi
2014-07-15 14:38 ` Pedro Alves [this message]
2014-07-16 2:19 ` Yao Qi
2014-07-16 5:19 ` Yao Qi
2014-07-16 19:02 ` 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=53C537A1.9080802@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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