From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10597 invoked by alias); 11 Feb 2020 17:04:01 -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 10581 invoked by uid 89); 11 Feb 2020 17:04:01 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mail-ot1-f65.google.com Received: from mail-ot1-f65.google.com (HELO mail-ot1-f65.google.com) (209.85.210.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Feb 2020 17:03:59 +0000 Received: by mail-ot1-f65.google.com with SMTP id d3so10826112otp.4 for ; Tue, 11 Feb 2020 09:03:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/UV8O4n2QoCgdc5p3tqASj1NamVSmPUoDKyeqlOmEn4=; b=Rq4mOSvy8/2sGeDMxqw33RRshN7MSslTZi0qjpDBoBzkusiQ0qHnc2kyxkw7bffm06 Shw/6Ws/d63pQpQGt3YPoAtiLegSzjxa79z/RosnCnVqU8DTqtoQe+gnD/J8eJTrPW9c IUS7ASpi5X/AtvgxwwJcLDtySldD590YfZ1s+q5TDwQVxNQ3CPdWUJyG6O2MlZWa9t3n fOW7czxIFiXrlt5EmD2WGIZgz0/K3nalEEE3Nz8hxDY//fq7iV3JZSFEa/vK+Zd8cLt2 10fQRQH73lvTVXpreng1hxQNwmYcqd8QyI8dqhDobOJDBXbGBzIbQOs1eNvkpa9UkRWI YEyg== MIME-Version: 1.0 References: <20200210142435.397899-1-hjl.tools@gmail.com> <20200210230156.GR5669@bubble.grove.modra.org> In-Reply-To: From: "H.J. Lu" Date: Tue, 11 Feb 2020 17:04:00 -0000 Message-ID: Subject: Re: [PATCH] Use GCC LTO wrapper to get real symbols from LTO IR objects To: Michael Matz Cc: Alan Modra , Binutils Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00193.txt.bz2 On Tue, Feb 11, 2020 at 8:07 AM Michael Matz wrote: > > Hi, > > On Mon, 10 Feb 2020, H.J. Lu wrote: > > > > Wow, that's a lot of work to get proper symbol type. What happens if > > > > Very true. I couldn't come up with a better solution without changing > > plugin API. > > Then, it should perhaps be changed? The cure without that (i.e. your > patch) looks worse than the disease (temporary files, hardcoding path > layouts, dependence on gcc installed) :-/ > > I know why you wrote the patch as is, but ... ugh. I think plugin API should be extended. In the meantime, we have a problem to solve. -- H.J.