public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Sriraman Tallam <tmsriram@google.com>
Cc: Cary Coutant <ccoutant@google.com>, binutils <binutils@sourceware.org>
Subject: Re: [patch] Gold linker patch to provide plugin support for mapping some text sections to an unique ELF segment.
Date: Fri, 24 Aug 2012 17:41:00 -0000	[thread overview]
Message-ID: <CAKOQZ8yxdYMJijEC1RbRxhBV9rpdmMOaqxTnn8W0+Qcz8i3q2g@mail.gmail.com> (raw)
In-Reply-To: <CAAs8HmwCE61Mex95HWC0+ji1=QrziV7dwpAO0BZZpx0QOY8QhA@mail.gmail.com>

On Wed, Aug 22, 2012 at 8:12 PM, Sriraman Tallam <tmsriram@google.com> wrote:
> Hi Ian,
>
>     I have made all the changes and attached the patch.

> +  flags = this->get_output_section_flags (flags);

No space before parenthesis.

> +    // Identifier for the Segment.  ELF Segments dont have names.
> +    const char* name;
> +    // Additional Segment flags.

s/Segment/segment/ three times.

> +  void
> +  set_segment_alignment(uint64_t align)
> +  { this->segment_alignment_ = align; }
> +
> +

Only one blank line here.

> +/* The linker's interface for specifying that a specific set of sections
> +   must be mapped to a unique segment.  ELF segments do not have names
> +   and the NAME is used as an identifier only.

As I understand it, this comment isn't precisely accurate.  It's true
that ELF segments don't have names, but NAME is used as the name of
the newly created output section that is then placed in the unique
PT_LOAD segment.  Please fix accordingly.

This patch is OK with those changes.

Thanks.

Ian

  reply	other threads:[~2012-08-24  6:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21  0:28 Sriraman Tallam
2012-07-31 17:21 ` Sriraman Tallam
2012-08-03  6:44   ` Cary Coutant
2012-08-10  0:56     ` Sriraman Tallam
2012-08-22 21:41       ` Ian Lance Taylor
2012-08-23  4:14         ` Sriraman Tallam
2012-08-24 17:41           ` Ian Lance Taylor [this message]
2012-08-24 17:44           ` Cary Coutant
2012-08-24 19:01             ` Sriraman Tallam

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=CAKOQZ8yxdYMJijEC1RbRxhBV9rpdmMOaqxTnn8W0+Qcz8i3q2g@mail.gmail.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=tmsriram@google.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).