From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17028 invoked by alias); 10 Sep 2014 22:05:30 -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 17004 invoked by uid 89); 10 Sep 2014 22:05:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-oa0-f53.google.com Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 10 Sep 2014 22:05:28 +0000 Received: by mail-oa0-f53.google.com with SMTP id eb12so13792350oac.12 for ; Wed, 10 Sep 2014 15:05:26 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.73.231 with SMTP id o7mr48266843obv.56.1410386726640; Wed, 10 Sep 2014 15:05:26 -0700 (PDT) Received: by 10.202.106.205 with HTTP; Wed, 10 Sep 2014 15:05:26 -0700 (PDT) In-Reply-To: References: <20140330042516.1A88E74481@topped-with-meat.com> <20140330045552.GX18201@bubble.grove.modra.org> <20140330050615.7DC5774481@topped-with-meat.com> <20140331200446.A09B074430@topped-with-meat.com> <20140331214025.E61517447E@topped-with-meat.com> Date: Wed, 10 Sep 2014 22:05:00 -0000 Message-ID: Subject: Re: gold vs libc From: =?UTF-8?Q?Rafael_Esp=C3=ADndola?= To: Cary Coutant Cc: Ian Lance Taylor , Roland McGrath , Alan Modra , "GNU C. Library" , Binutils Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-09/txt/msg00081.txt.bz2 > If the .eh_frame data in crt1.o really does need to come before > __EH_FRAME_BEGIN__, another thing you could do is simply make it so > gold treats it as non-optimizable. Adding a null relocation to the > first word of the section should do it; inserting a zero-length entry > anywhere but the end would do it (if that doesn't have adverse affects > elsewhere). Since the problem comes from an optimizations that knows what .eh_frame is, maybe it could learn that __EH_FRAME_BEGIN__ and __EH_FRAME_END__ are special symbols marking the start and end of the section? Cheers, Rafael