From: Will Newton <will.newton@linaro.org>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH]Fix aarch64 native build issue caused by use of LONGEST
Date: Thu, 21 Aug 2014 08:40:00 -0000 [thread overview]
Message-ID: <CANu=DmjYhc6tHUyLy=jkuug8WMiyqRmJL+Pq08sRzGzvZPwKQA@mail.gmail.com> (raw)
In-Reply-To: <CAHFci28bntUtNPyibqBPmcyM+nmo=t534tBvgtabcFot=ZXfTw@mail.gmail.com>
On 21 August 2014 09:32, Bin.Cheng <amker.cheng@gmail.com> wrote:
> Hi,
> Recent gdb code refactor changes LONGEST from a macro to a typedef,
> thus the use of it in aarch64-linux-nat.c is no longer valid.
>
> This patch fixes the build failure which is obvious. Is it OK?
>
> Thanks,
> bin
>
> 2014-08-21 Bin Cheng <bin.cheng@arm.com>
>
> * aarch64-linux-nat.c (dr_changed_t): Change the type from
> unsigned LONGEST to ULONGEST.
I pushed this as obvious given that Marcus is not around.
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2014-08-21 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:32 Bin.Cheng
2014-08-21 8:40 ` Will Newton [this message]
2014-08-27 8:46 ` Gary Benson
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='CANu=DmjYhc6tHUyLy=jkuug8WMiyqRmJL+Pq08sRzGzvZPwKQA@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=amker.cheng@gmail.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