From: Nick Alcock <nick.alcock@oracle.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PATCH v2 00/19] libctf, and CTF support for objdump and readelf
Date: Mon, 20 May 2019 20:50:00 -0000 [thread overview]
Message-ID: <87pnocg8ae.fsf@esperi.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.1905201923270.19503@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 20 May 2019 19:27:04 +0000")
On 20 May 2019, Joseph Myers uttered the following:
> On Fri, 17 May 2019, Nick Alcock wrote:
>
>> Joseph: you'll probably be interested in patches 3, 9, 10, and 15 in particular,
>> for their BFDization and portability fixes.
>
> Thanks. A quick question would be what hosts you've tested this builds
> for. At least some GNU/Linux distributions package cross-compilers for
> MinGW; if you install such a compiler and make sure that binutils, with
> these patches, can build using it, --host=x86_64-w64-mingw32
> --target=<some ELF target> (adjust host as needed if the host triplet of
> the packaged compiler is different), then there shouldn't be major
> problems getting it to build on any other likely host either.
Oh blast I knew I forgot to mention something.
This has mostly been tested on Linux (x86_64, arm64, and sparc64): I did
do a native mingw build a while back (right after doing the mmap and
pread stuff) but I probably need to do another one. I'm tempted to do a
FreeBSD build too simply because it's easy.
I did most of the no-mmap and no-pread() testing on Linux, by just
hacking the config.h to turn it off and making sure it wasn't making the
relevant syscalls any more, and still worked. (Which it does, but it's
slower when doing archive opens, unsurprisingly, since it's reading the
whole archive in even if only a bit is needed.)
I suspect the bfd side of things is still broken: a teammate has just
tested it and reported that things aren't working there yet. I'll look
at that tomorrow.
next prev parent reply other threads:[~2019-05-20 20:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 22:10 Nick Alcock
2019-05-17 22:10 ` [PATCH v2 14/19] libctf: library version enforcement Nick Alcock
2019-05-17 22:10 ` [PATCH v2 08/19] libctf: creation functions Nick Alcock
2019-05-29 14:09 ` Szabolcs Nagy
2019-05-29 14:19 ` Nick Alcock
2019-05-17 22:10 ` [PATCH v2 13/19] libctf: type copying Nick Alcock
2019-05-17 22:10 ` [PATCH v2 04/19] libctf: low-level list manipulation and helper utilities Nick Alcock
2019-05-17 22:10 ` [PATCH v2 09/19] libctf: opening Nick Alcock
2019-05-17 22:10 ` [PATCH v2 02/19] include: new header ctf-api.h Nick Alcock
2019-05-17 22:10 ` [PATCH v2 10/19] libctf: ELF file opening via BFD Nick Alcock
2019-05-17 22:10 ` [PATCH v2 05/19] libctf: error handling Nick Alcock
2019-05-17 22:10 ` [PATCH v2 12/19] libctf: lookups by name and symbol Nick Alcock
2019-05-17 22:10 ` [PATCH v2 07/19] libctf: implementation definitions related to file creation Nick Alcock
2019-05-17 22:10 ` [PATCH v2 01/19] include: new header ctf.h: file format description Nick Alcock
2019-05-17 22:10 ` [PATCH v2 17/19] libctf: debug dumping Nick Alcock
2019-05-17 22:10 ` [PATCH v2 03/19] libctf: lowest-level memory allocation and debug-dumping wrappers Nick Alcock
2019-05-17 22:10 ` [PATCH v2 15/19] libctf: mmappable archives Nick Alcock
2019-05-17 22:10 ` [PATCH v2 19/19] binutils: CTF support for objdump and readelf Nick Alcock
2019-05-17 22:10 ` [PATCH v2 06/19] libctf: hashing Nick Alcock
2019-05-17 22:11 ` [PATCH v2 18/19] libctf: build system Nick Alcock
2019-05-17 22:12 ` [PATCH v2 11/19] libctf: core type lookup Nick Alcock
2019-05-17 22:12 ` [PATCH v2 16/19] libctf: labels Nick Alcock
2019-05-20 19:27 ` [PATCH v2 00/19] libctf, and CTF support for objdump and readelf Joseph Myers
2019-05-20 20:50 ` Nick Alcock [this message]
2019-05-28 8:33 ` Nick Clifton
2019-05-28 9:56 ` Nick Alcock
2019-05-28 16:39 ` Jose E. Marchesi
2019-05-28 19:16 ` Christophe Lyon
2019-05-28 21:36 ` Nix
2019-05-29 3:25 ` Alan Modra
2019-05-29 9:14 ` Jose E. Marchesi
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=87pnocg8ae.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.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).