public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 2/6] bfd: prune COFF/PE section flags setting
Date: Thu, 4 Mar 2021 15:17:27 +1030	[thread overview]
Message-ID: <20210304044727.GQ6042@bubble.grove.modra.org> (raw)
In-Reply-To: <f78289bf-1e65-f502-ed4d-fad8fe477acd@suse.com>

On Tue, Mar 02, 2021 at 10:47:44AM +0100, Jan Beulich via Binutils wrote:
> It is my understanding that IMAGE_SCN_LNK_* are supposed to communicate
> information to the (static) linker, and become at best meaningless in PE
> images. I wouldn't call loaders wrong which would refuse to process
> sections with any of these bits set. While there's no replacement for
> IMAGE_SCN_LNK_COMDAT, use IMAGE_SCN_MEM_DISCARDABLE in place of
> IMAGE_SCN_LNK_REMOVE in this case.
> 
> bfd/
> 2021-02-XX  Jan Beulich  <jbeulich@suse.com>
> 
> 	* coffcode.h (sec_to_styp_flags): Don't set IMAGE_SCN_LNK_* in
> 	final PE images.

OK.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2021-03-04  4:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  9:46 [PATCH 0/6] PE/COFF linking adjustments Jan Beulich
2021-03-02  9:47 ` [PATCH 1/6] ld: don't generate base relocations in PE output for absolute symbols Jan Beulich
2021-03-02 13:30   ` Jan Beulich
2021-03-04  4:46   ` Alan Modra
2021-03-04  8:52     ` Jan Beulich
2021-03-04 13:16       ` Alan Modra
2021-03-05 12:49         ` Alan Modra
2021-03-05 13:38           ` Jan Beulich
2021-03-05 13:59             ` Alan Modra
2021-03-02  9:47 ` [PATCH 2/6] bfd: prune COFF/PE section flags setting Jan Beulich
2021-03-04  4:47   ` Alan Modra [this message]
2021-03-02  9:48 ` [PATCH 3/6] bfd: refine handling of relocations between debugging sections Jan Beulich
2021-03-04  6:10   ` Alan Modra
2021-03-04  9:00     ` Jan Beulich
2021-03-05 12:00       ` Alan Modra
2021-03-08 14:17         ` Jan Beulich
2021-03-09  2:24           ` Alan Modra
2021-03-09  7:46             ` Jan Beulich
2021-03-09 11:23               ` Alan Modra
2021-03-09 12:49             ` Jan Beulich
2021-03-02  9:49 ` [PATCH 4/6] ld: adjust ld-scripts/map-address.* Jan Beulich
2021-03-04  6:10   ` Alan Modra
2021-03-02  9:49 ` [PATCH 5/6] bfd: don't silently wrap or truncate PE image section RVAs Jan Beulich
2021-03-04  6:13   ` Alan Modra
2021-03-02  9:50 ` [PATCH 6/6] bfd: strip symbols not representable in COFF/PE symbol table Jan Beulich
2021-03-04  6:15   ` Alan Modra
2021-03-04  9:06     ` Jan Beulich
2021-03-04 13:27       ` Alan Modra
2021-03-08 15:05       ` Jan Beulich
2021-03-08 16:11         ` 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=20210304044727.GQ6042@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.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).