public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: binutils@sourceware.org
Subject: Re: SEC_NEVER_LOAD cleanup
Date: Sun, 17 Oct 2010 16:40:00 -0000	[thread overview]
Message-ID: <4CBB2C5A.4020401@gmail.com> (raw)
In-Reply-To: <AANLkTikPFJV1+KYqyfRMJWVbm02ykVrtqPxJfj=UKHsa@mail.gmail.com>

On 17/10/2010 11:32, Kai Tietz wrote:

> Well, the CONTENT flag is here of less use. The underlying issue is
> (at least for pe-coff) that SEC_NEVER_LOAD (which indicates for
> pe-coff just that this section doesn't have load and allocation flags
> set and will not loaded into memory - btw different to discard flag,
> which means that it is initially loaded but then discarded) is treated
> similar to SEC_EXCLUDE. The SEC_EXCLUDE is in fact the PE-COFF flag
> IMAGE_SCN_LNK_REMOVE.
> This looks wrong to me. If you want I can prepare a patch for this.

  Thanks, that would be very helpful.

    cheers,
      DaveK

  reply	other threads:[~2010-10-17 16:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16  0:03 Alan Modra
2010-10-15 20:31 ` Dave Korn
2010-10-15 20:36   ` Kai Tietz
2010-10-15 22:27     ` Dave Korn
2010-10-15 22:28       ` Dave Korn
2010-10-16  2:36   ` Alan Modra
2010-10-16 20:08     ` Kai Tietz
2010-10-16 20:19       ` Dave Korn
2010-10-17 10:32         ` Kai Tietz
2010-10-17 16:40           ` Dave Korn [this message]
2010-10-17 19:18             ` Kai Tietz
2010-10-17 23:29       ` Alan Modra
2010-10-18  6:22         ` Kai Tietz
2010-10-18 13:44           ` Alan Modra
2010-10-18 14:39             ` Kai Tietz
2010-10-19 15:05               ` Kai Tietz
2010-10-20 14:48                 ` Dave Korn
2010-10-26 12:46                   ` Alan Modra
2010-10-26 16:56                     ` Dave Korn
2010-11-05  4:36                     ` Dave Korn
2010-11-05  5:58                       ` Alan Modra
2010-11-05  7:24                         ` Dave Korn
2010-10-21 23:32     ` Alan Modra

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=4CBB2C5A.4020401@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ktietz70@googlemail.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).