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, 02 Mar 2015 16:03:00 -0000 [thread overview]
Message-ID: <CAMe9rOoA+KFRi=gm4ui8iPP+y17G5hbsyannwyB0QCJqAnVG0g@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOovN+kmzU=0b1L3Gwq-AbHm5Y=YKy1LdOHw35G9PR8cUQ@mail.gmail.com>
On Mon, Jan 26, 2015 at 9:21 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Wed, Jan 7, 2015 at 10:50 AM, Cary Coutant <ccoutant@google.com> wrote:
>> Thanks for looking at this, but I find this a bit much for what it
>> does -- it's pretty intrusive, and still doesn't even do the right
>> thing with the eh info from crt1.o (which is still placed before the
>> __EH_FRAME_BEGIN__ symbol, and will be ignored).
>>
>> I really dislike special-cases based on filename. At one point in the
>> discussion, Roland suggested recognizing crtbeginT.o by the fact that
>> it has a relocation to the .eh_frame section symbol. I think it may be
>> even simpler than that, though -- given that the endcap in crtend.o
>> has a non-zero length, I think it's safe to put all zero-length
>> .eh_frame sections in front of the optimized data. That should have
>> the desired affect for crtbeginT.o. Let me give that a try.
>>
>
> Hi Cary,
>
> Do we have any progress on this?
>
Any progress?
--
H.J.
next prev parent reply other threads:[~2015-03-02 16:03 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 [this message]
2015-03-09 17:16 ` Cary Coutant
2015-03-09 17:22 ` H.J. Lu
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='CAMe9rOoA+KFRi=gm4ui8iPP+y17G5hbsyannwyB0QCJqAnVG0g@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).