From: Joel Brobecker <brobecker@adacore.com>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: Backport of patch to gdb 8.0 branch.
Date: Fri, 18 May 2018 18:50:00 -0000 [thread overview]
Message-ID: <20180518170017.fjqa27umztktv7fx@adacore.com> (raw)
In-Reply-To: <20180518094554.GA18416@arm.com>
> This patch already exists in master and 8.1 branches as
> 957f6b39cab6cac0e4c54e650c7f75109544ac1d.
>
> Ok for gdb-8.0-branch?
>
> opcodes/
> 2018-05-18 Tamar Christina <tamar.christina@arm.com>
>
> PR gdb/23200
> * aarch64-opc.c (aarch64_logical_immediate_p): Update
> DEBUG_TRACE arguments.
Yes, you can go right ahead.
> diff --git a/opcodes/aarch64-opc.c b/opcodes/aarch64-opc.c
> index cc99c101236c542ff94bb9c0abc09df521ced330..a52ea70c0093f7daaecfd58e3f0e81a3953abf5f 100644
> --- a/opcodes/aarch64-opc.c
> +++ b/opcodes/aarch64-opc.c
> @@ -1204,8 +1204,8 @@ aarch64_logical_immediate_p (uint64_t value, int esize, aarch64_insn *encoding)
> uint64_t upper;
> int i;
>
> - DEBUG_TRACE ("enter with 0x%" PRIx64 "(%" PRIi64 "), is32: %d", value,
> - value, is32);
> + DEBUG_TRACE ("enter with 0x%" PRIx64 "(%" PRIi64 "), esize: %d", value,
> + value, esize);
>
> if (initialized == FALSE)
> {
>
--
Joel
prev parent reply other threads:[~2018-05-18 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR08MB0540BEEB7FDED47D0FE9D6DCFF930@HE1PR08MB0540.eurprd08.prod.outlook.com>
2018-05-16 13:54 ` Tamar Christina
2018-05-17 13:23 ` Tamar Christina
2018-05-17 19:39 ` Joel Brobecker
2018-05-18 10:57 ` Tamar Christina
2018-05-18 18:50 ` Joel Brobecker [this message]
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=20180518170017.fjqa27umztktv7fx@adacore.com \
--to=brobecker@adacore.com \
--cc=Tamar.Christina@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).