From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: Re: [PATCH 0/3] coff-go32-exe: support variable-length stubs
Date: Thu, 2 Apr 2020 14:34:22 +0100 [thread overview]
Message-ID: <bbbaa1b4-1e77-9b6e-b572-50c41648b948@redhat.com> (raw)
In-Reply-To: <20200319191923.34747-1-jwjagersma@gmail.com>
Hi Jan,
> This series includes three patches: The first changes the meaning of
> the bfd->origin field slightly, so that target code can use this to
> specify an offset into the file where the actual bfd is located.
> The second patch then uses this to enable support for variable-sized
> stubs in the coff-go32-exe format.
> The final patch is only a cleanup, it normalizes function and variable
> names in coff-stgo32.c so that they all begin with the same prefix.
Patch series approved and applied. (Including part 4 of 3...)
Cheers
Nick
prev parent reply other threads:[~2020-04-02 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 19:19 J.W. Jagersma
2020-03-19 19:19 ` [PATCH 1/3] always add base bfd->origin to file offset J.W. Jagersma
2020-03-19 19:19 ` [PATCH 2/3] coff-go32-exe: support variable-length stubs J.W. Jagersma
2020-03-19 19:19 ` [PATCH 3/3] normalize names in coff-stgo32.c J.W. Jagersma
2020-03-20 14:04 ` [PATCH 0/3] coff-go32-exe: support variable-length stubs Nick Clifton
2020-03-20 15:38 ` J.W. Jagersma
2020-03-20 19:42 ` DJ Delorie
2020-03-21 16:07 ` J.W. Jagersma
2020-04-01 16:45 ` J.W. Jagersma
2020-03-25 17:54 ` [PATCH 4/3+] coff-go32-exe: avoid reallocating stub on copy J.W. Jagersma
2020-04-02 13:34 ` Nick Clifton [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=bbbaa1b4-1e77-9b6e-b572-50c41648b948@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).