From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <binutils@sourceware.org>, <gdb-patches@sourceware.org>,
Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH] GDB/opcodes: Remove arch/mach/endian disassembler assertions
Date: Thu, 03 Aug 2017 11:36:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1708031235270.17596@tp.orcam.me.uk> (raw)
In-Reply-To: <86pocc3oam.fsf@gmail.com>
On Thu, 3 Aug 2017, Yao Qi wrote:
> I prefer to keep these asserts, as they could check the inconsistent
> uses of disassemble_info between gdb and opcodes. There is another
> assert for target armv5te, PR 21818, but the assert exposes an improper
> or unexpected usage of disassemble_info.mach in opcodes/arm-dis.c. I am
> fixing it.
How does the retaining of these assertions interact with `set
architecture' and `set endian' then?
Maciej
next prev parent reply other threads:[~2017-08-03 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 16:39 Maciej W. Rozycki
2017-08-03 11:04 ` Yao Qi
2017-08-03 11:36 ` Maciej W. Rozycki [this message]
2017-08-03 12:25 ` Maciej W. Rozycki
2017-08-04 10:49 ` Yao Qi
2017-08-07 13:24 ` Alan Modra
2017-08-07 14:56 ` Maciej W. Rozycki
2017-08-07 15:05 ` H.J. Lu
2017-08-07 15:15 ` Maciej W. Rozycki
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=alpine.DEB.2.00.1708031235270.17596@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--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