From: Alan Modra <amodra@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
sergiodj+buildbot@sergiodj.net, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB
Date: Thu, 15 Dec 2016 23:03:00 -0000 [thread overview]
Message-ID: <20161215230316.GM10584@bubble.grove.modra.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1612151946340.6743@tp.orcam.me.uk>
On Thu, Dec 15, 2016 at 08:09:42PM +0000, Maciej W. Rozycki wrote:
> I'll see if there is something I could do right away as a temporary
> measure to unbreak 32-bit BFD configurations -- I would make the reference
> from `opcodes/mips-dis.c' to `bfd_mips_elf_get_abiflags' weak, however
> regrettably this does not appear supported, so maybe we'll require a dummy
> stub or suchlike hackery if MIPS target support is enabled, but not
> included in BFD.
Make the new ELF code in mips-dis.c conditional on BFD64?
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2016-12-15 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cHNui-0007Mp-46@kwanyin.sergiodj.net>
2016-12-15 12:16 ` Maciej W. Rozycki
2016-12-15 19:04 ` Antoine Tremblay
2016-12-15 20:10 ` Maciej W. Rozycki
2016-12-15 23:03 ` Alan Modra [this message]
2016-12-15 23:19 ` Maciej W. Rozycki
2016-12-19 11:49 ` Maciej W. Rozycki
[not found] ` <20161222123958.GA2896@bubble.grove.modra.org>
[not found] ` <alpine.DEB.2.00.1612222017020.6743@tp.orcam.me.uk>
2016-12-27 10:08 ` [PATCH, RFA] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD Joel Brobecker
2016-12-28 12:11 ` Alan Modra
2016-12-30 6:44 ` Joel Brobecker
2016-12-31 9:15 ` Maciej W. Rozycki
2016-12-15 19:47 ` Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB Yao Qi
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=20161215230316.GM10584@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
--cc=sergiodj+buildbot@sergiodj.net \
/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