From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25174 invoked by alias); 2 Mar 2015 16:03:28 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 25161 invoked by uid 89); 2 Mar 2015 16:03:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-oi0-f50.google.com Received: from mail-oi0-f50.google.com (HELO mail-oi0-f50.google.com) (209.85.218.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 02 Mar 2015 16:03:23 +0000 Received: by mail-oi0-f50.google.com with SMTP id v1so27762432oia.9 for ; Mon, 02 Mar 2015 08:03:22 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.78.72 with SMTP id z8mr19621216oew.13.1425312201986; Mon, 02 Mar 2015 08:03:21 -0800 (PST) Received: by 10.76.134.102 with HTTP; Mon, 2 Mar 2015 08:03:21 -0800 (PST) In-Reply-To: References: <20140331200446.A09B074430@topped-with-meat.com> <20140331214025.E61517447E@topped-with-meat.com> <20140910225238.0B6362C39CF@topped-with-meat.com> <20141220135811.GA7161@gmail.com> <20150107131655.GA7818@gmail.com> <20150107144300.GA498@gmail.com> Date: Mon, 02 Mar 2015 16:03:00 -0000 Message-ID: Subject: Re: PATCH: PR gold/14675: No eh_frame info registered in exception_static_test From: "H.J. Lu" To: Cary Coutant Cc: Ian Lance Taylor , Roland McGrath , Alan Modra , Binutils , =?UTF-8?Q?Rafael_=C3=81vila_de_Esp=C3=ADndola?= Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-03/txt/msg00004.txt.bz2 On Mon, Jan 26, 2015 at 9:21 AM, H.J. Lu wrote: > On Wed, Jan 7, 2015 at 10:50 AM, Cary Coutant 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.