public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Rafael Espíndola" <rafael.espindola@gmail.com>
To: Binutils <binutils@sourceware.org>
Cc: Cary Coutant <ccoutant@gmail.com>
Subject: Re: [patch][gold] Change how we compute merge mapping for strings
Date: Thu, 04 Jun 2015 13:19:00 -0000	[thread overview]
Message-ID: <CAG3jReKoapF9m86xHgyc8f3P43+Qx=eEreonry1r+Lnxce_b_w@mail.gmail.com> (raw)
In-Reply-To: <CAG3jReKedNNeO-zGWsoeW_N9xETZBjYsOcmdCixReaYKzJKGBg@mail.gmail.com>

ping

On 27 May 2015 at 11:27, Rafael Espíndola <rafael.espindola@gmail.com> wrote:
> ping
>
> On 20 May 2015 at 11:13, Rafael Espíndola <rafael.espindola@gmail.com> wrote:
>> Now with the correct email address. Sorry about that.
>>
>> On 20 May 2015 at 11:12, Rafael Espíndola <rafael.espindola@gmail.com> wrote:
>>> Currently we first record the offset and hash of each string. We then
>>> walk that computing the size from the difference in the offsets.
>>>
>>> This doesn't work if not every string is kept, which is what I am
>>> trying to do (gc unused parts of SHF_MERGE sections).
>>>
>>> With the attached patch we first add a mapping that is missing the
>>> output offset and once the strings are merged we just set the output
>>> offset.
>>>
>>> Cheers,
>>> Rafael
>>>
>>> 2015-05-20  Rafael Ávila de Espíndola <rafael.espindola@gmail.com>
>>>
>>> * merge.cc (do_add_input_section): Create mappings with no output
>>> offset.
>>> (finalize_merged_data): Set the output offsets.
>>> * merge.h (Merged_string): Delete.

      reply	other threads:[~2015-06-04 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 15:12 Rafael Espíndola
2015-05-20 15:13 ` Rafael Espíndola
2015-05-27 15:27   ` Rafael Espíndola
2015-06-04 13:19     ` Rafael Espíndola [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='CAG3jReKoapF9m86xHgyc8f3P43+Qx=eEreonry1r+Lnxce_b_w@mail.gmail.com' \
    --to=rafael.espindola@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@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).