From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"vapier@gentoo.org" <vapier@gentoo.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Remove MAX_REGISTER_SIZE from remote-sim.c
Date: Fri, 24 Mar 2017 11:41:00 -0000 [thread overview]
Message-ID: <611F99A8-55EA-45B6-B9EC-DE69F21EEFF8@arm.com> (raw)
In-Reply-To: <86wpbft0r4.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 834 bytes --]
> On 24 Mar 2017, at 10:41, Yao Qi <qiyaoltc@gmail.com> wrote:
>
> Alan Hayward <Alan.Hayward@arm.com> writes:
>
>> Used a std::vector in the first case and struct value in the second.
>>
>> Tested using make check with board files unix and native-gdbserver.
>>
>
> What is your target triplet? Do you see remote-sim.o in your build
> directory? remote-sim.c may not be built at all.
Youâre correct - Iâm not building remote-sim at all!
Forcing SIM_OBS in Makefile.in gives me a compile error (just need to
cast result of value_contents_all to remove the const).
Is there an easy way to build and test remote-sim ?
>
>> Ok to commit?
>>
>
> It is good to me. This patch is related to SIM, so I'd like Mike to
> take a look too.
>
> --
> Yao (é½å°§)
\x16º&Öéj×!zÊÞ¶êç×~ûóÙb²Ö«r\x18\x1dnr\x17¬
next prev parent reply other threads:[~2017-03-24 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 10:03 Alan Hayward
2017-03-23 14:12 ` Alan Hayward
[not found] ` <86wpbft0r4.fsf@gmail.com>
2017-03-24 11:41 ` Alan Hayward [this message]
[not found] ` <E7F813B0-BCB9-464C-BD4C-95F0A3D789E1@arm.com>
[not found] ` <CAH=s-POSw=RatBGkLmryoAR4eN880nzxW+zt-p_TOuPMq8RRaw@mail.gmail.com>
2017-06-26 12:41 ` Alan Hayward
2017-06-27 10:57 ` Yao Qi
2017-06-27 12:14 ` Alan Hayward
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=611F99A8-55EA-45B6-B9EC-DE69F21EEFF8@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=qiyaoltc@gmail.com \
--cc=vapier@gentoo.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