public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Sriraman Tallam <tmsriram@google.com>
To: Cary Coutant <ccoutant@google.com>
Cc: binutils <binutils@sourceware.org>, Ian Lance Taylor <iant@google.com>
Subject: Re: ICF on PowerPC Bug
Date: Thu, 03 Apr 2014 00:11:00 -0000	[thread overview]
Message-ID: <CAAs8Hmy=HaC3QVK7WPDCO-DQYoRRt7FpsC_-GbpUB+WjHfnT=w@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4okBwRJX8wAQ8i3cwfRzxphpV+OVcDmN9=8fbg45HOaBw@mail.gmail.com>

Committed with those changes.

Thanks
Sri

On Wed, Apr 2, 2014 at 2:12 PM, Cary Coutant <ccoutant@google.com> wrote:
>> Attached patch to fix the PPC ICF problem by using references to the
>> reloc info vectors. Ok to commit?
>
> -      Icf::Sections_reachable_info v =
> +      Icf::Sections_reachable_info &v =
>          (it_reloc_info_list->second).section_info;
>        // Stores the information of the symbol pointed to by the reloc.
> -      Icf::Symbol_info s = (it_reloc_info_list->second).symbol_info;
> +      Icf::Symbol_info &s = (it_reloc_info_list->second).symbol_info;
>        // Stores the addend and the symbol value.
> -      Icf::Addend_info a = (it_reloc_info_list->second).addend_info;
> +      Icf::Addend_info &a = (it_reloc_info_list->second).addend_info;
>        // Stores the offset of the reloc.
> -      Icf::Offset_info o = (it_reloc_info_list->second).offset_info;
> -      Icf::Reloc_addend_size_info reloc_addend_size_info =
> +      Icf::Offset_info &o = (it_reloc_info_list->second).offset_info;
> +      Icf::Reloc_addend_size_info &reloc_addend_size_info =
>          (it_reloc_info_list->second).reloc_addend_size_info;
>        Icf::Sections_reachable_info::iterator it_v = v.begin();
>        Icf::Symbol_info::iterator it_s = s.begin();
>
> Except for v and a, I think these can all be const, and their
> iterators can be const_iterators. OK with those changes.
>
> Thanks!
>
> -cary

      reply	other threads:[~2014-04-03  0:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 22:06 Sriraman Tallam
2014-04-02  6:54 ` Alan Modra
2014-04-02 16:49   ` Sriraman Tallam
2014-04-02 19:11     ` Sriraman Tallam
2014-04-02 21:12       ` Cary Coutant
2014-04-03  0:11         ` Sriraman Tallam [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='CAAs8Hmy=HaC3QVK7WPDCO-DQYoRRt7FpsC_-GbpUB+WjHfnT=w@mail.gmail.com' \
    --to=tmsriram@google.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=iant@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).