public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Cary Coutant <ccoutant@google.com>
Cc: "Ian Lance Taylor" <iant@google.com>,
	"Roland McGrath" <roland@hack.frob.com>,
	"Alan Modra" <amodra@gmail.com>,
	Binutils <binutils@sourceware.org>,
	"Rafael Ávila de Espíndola" <rafael.espindola@gmail.com>
Subject: Re: PATCH: PR gold/14675: No eh_frame info registered in exception_static_test
Date: Mon, 09 Mar 2015 17:22:00 -0000	[thread overview]
Message-ID: <CAMe9rOpGOAAcA3-GkOxB45JSOfS9TdKCYHX6-4F=BOf-XJ+xcw@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4ojEwA+BXrRm8U_QNoXkxHmA0KY7kib=6wFQNjOmEMTWA@mail.gmail.com>

On Mon, Mar 9, 2015 at 10:16 AM, Cary Coutant <ccoutant@google.com> wrote:
>> Any progress?
>
> I've committed the attached patch to fix this problem by delaying the
> attachment of the optimized .eh_frame sections to the output section
> until we see the end marker section (or to the end of pass 1 if we
> never see an end marker).
>
> -cary
>
>
> 2015-03-09  Cary Coutant  <ccoutant@google.com>
>
> gold/
>         PR gold/14675
>         * ehframe.cc (Eh_frame::add_ehframe_input_section): Change return type;
>         return enum indicating whether .eh_frame section is empty, optimizable,
>         unrecognized, or an end marker. Adjust explicit instantiations.
>         * ehframe.h (Eh_frame::Eh_frame_section_disposition): New enum type.
>         (Eh_frame::add_ehframe_input_section): Change return type.
>         * gold.cc (queue_middle_tasks): Call Layout::finalize_eh_frame_section.
>         * layout.cc (Layout::layout_eh_frame): Don't add optimized sections
>         to the .eh_frame output section until we see the end marker.
>         (Layout::finalize_eh_frame_section): New.
>         * layout.h: (Layout::finalize_eh_frame_section): New.

Thanks.

-- 
H.J.

  reply	other threads:[~2015-03-09 17:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30  4:25 gold vs libc Roland McGrath
2014-03-30  4:56 ` Alan Modra
2014-03-30  5:09   ` Roland McGrath
2014-03-31 19:03     ` Ian Lance Taylor
2014-03-31 20:04       ` Roland McGrath
2014-03-31 20:53         ` Ian Lance Taylor
2014-03-31 21:40           ` Roland McGrath
2014-04-01 18:25             ` Ian Lance Taylor
2014-09-10 20:56               ` Cary Coutant
2014-09-10 22:05                 ` Rafael Espíndola
2014-09-11  0:32                   ` Alan Modra
2014-09-10 22:52                 ` Roland McGrath
2014-09-11  0:04                   ` Ian Lance Taylor
2014-12-20 13:58                     ` PATCH: PR gold/14675: No eh_frame info registered in exception_static_test H.J. Lu
2014-12-22 17:37                       ` Cary Coutant
2014-12-22 22:40                         ` H.J. Lu
2014-12-23  0:58                           ` H.J. Lu
2015-01-07 13:17                         ` H.J. Lu
2015-01-07 14:43                           ` H.J. Lu
2015-01-07 18:50                             ` Cary Coutant
2015-01-26 17:22                               ` H.J. Lu
2015-03-02 16:03                                 ` H.J. Lu
2015-03-09 17:16                                   ` Cary Coutant
2015-03-09 17:22                                     ` H.J. Lu [this message]
2015-03-20 15:41                                     ` H.J. Lu
2014-09-11 16:00                   ` gold vs libc Cary Coutant
2014-09-11 16:05                     ` Cary Coutant
2014-09-11 16:45                       ` Rafael Espíndola
2014-09-11 16:21                     ` Ian Lance Taylor
2014-09-11 18:33                     ` Roland McGrath
2014-03-30 18:28 ` Carlos O'Donell

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='CAMe9rOpGOAAcA3-GkOxB45JSOfS9TdKCYHX6-4F=BOf-XJ+xcw@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@google.com \
    --cc=iant@google.com \
    --cc=rafael.espindola@gmail.com \
    --cc=roland@hack.frob.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).