From: Luis Machado <lgustavo@codesourcery.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fixup gdb.python/py-value.exp for bare-metal aarch64-elf
Date: Mon, 10 Oct 2016 17:04:00 -0000 [thread overview]
Message-ID: <9ec466f7-ad95-18e6-c963-83c35399c7f5@codesourcery.com> (raw)
In-Reply-To: <dbcd9b91-df9d-b437-a33f-76801c369b04@codesourcery.com>
Hi Yao,
Given Martin's reply, do you think this is now acceptable with possibly
some minor fixups?
Luis
On 10/07/2016 11:59 AM, Luis Machado wrote:
> On 10/07/2016 11:51 AM, Yao Qi wrote:
>> Well, I am not a C standard guru, so I can be wrong. I post
>> this question to gcc-help
>> https://gcc.gnu.org/ml/gcc-help/2016-10/msg00031.html
>>
>
> That is ok. Let's see what comes out of that.
>
> Thanks,
> Luis
>
next prev parent reply other threads:[~2016-10-10 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 16:27 Luis Machado
2016-10-07 10:23 ` Yao Qi
2016-10-07 11:42 ` Luis Machado
2016-10-07 12:09 ` Luis Machado
2016-10-07 14:48 ` Yao Qi
2016-10-07 15:07 ` Luis Machado
2016-10-07 16:52 ` Yao Qi
2016-10-07 17:00 ` Luis Machado
2016-10-10 17:04 ` Luis Machado [this message]
2016-10-11 8:18 ` Yao Qi
2016-10-07 18:21 ` Kevin Buettner
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=9ec466f7-ad95-18e6-c963-83c35399c7f5@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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