public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: Dave Korn <dave.korn.cygwin@gmail.com>
Subject: [PATCH 0/5] PE/COFF: assorted adjustments
Date: Fri, 6 May 2022 08:53:08 +0200	[thread overview]
Message-ID: <4242b48a-f2c3-4af2-db1e-35dbbbdc1b2e@suse.com> (raw)

In the Xen Project we link the hypervisor both an an ELF binary and
as a native EFI one, all from largely the same (ELF) objects. On
top of earlier changes to make certain variants thereof (like
including debug in the EFI binary) a few more issues were noticed,
most related to the stripping of such binaries.

1: don't over-align file positions of PE executable sections
2: COFF: make objcopy / strip honor --keep-file-symbols
3: COFF/PE: don't leave zero timestamp after objcopy / strip
4: COFF/PE: keep linker version during objcopy / strip
5: COFF: use hash for string table also when copying / stripping

Jan


             reply	other threads:[~2022-05-06  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  6:53 Jan Beulich [this message]
2022-05-06  6:54 ` [PATCH 1/5] don't over-align file positions of PE executable sections Jan Beulich
2022-05-06  6:54 ` [PATCH 2/5] COFF: make objcopy / strip honor --keep-file-symbols Jan Beulich
2022-05-06  6:54 ` [PATCH 3/5] COFF/PE: don't leave zero timestamp after objcopy / strip Jan Beulich
2022-05-06  6:55 ` [PATCH 4/5] COFF/PE: keep linker version during " Jan Beulich
2022-05-06  6:55 ` [PATCH 5/5] COFF: use hash for string table also when copying / stripping Jan Beulich

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=4242b48a-f2c3-4af2-db1e-35dbbbdc1b2e@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=dave.korn.cygwin@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).