From: "H.J. Lu" <hjl.tools@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: Alan Modra <amodra@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] Use GCC LTO wrapper to get real symbols from LTO IR objects
Date: Tue, 11 Feb 2020 17:04:00 -0000 [thread overview]
Message-ID: <CAMe9rOpAgwgk8o2gyHYsd8rh7oCzS5J9Lv8-dU52b7S3krd5qA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2002111604240.25090@wotan.suse.de>
On Tue, Feb 11, 2020 at 8:07 AM Michael Matz <matz@suse.de> 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.
next prev parent reply other threads:[~2020-02-11 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 14:24 H.J. Lu
2020-02-10 21:31 ` H.J. Lu
2020-02-10 23:02 ` Alan Modra
2020-02-11 1:23 ` H.J. Lu
2020-02-11 2:31 ` Alan Modra
2020-02-11 12:21 ` H.J. Lu
2020-02-11 22:05 ` [PATCH] Plugin: Treat each object as independent H.J. Lu
2020-02-11 22:22 ` Alan Modra
2020-02-11 16:07 ` [PATCH] Use GCC LTO wrapper to get real symbols from LTO IR objects Michael Matz
2020-02-11 17:04 ` H.J. Lu [this message]
2020-02-13 8:15 ` Alan Modra
2020-03-10 14:55 ` Richard Biener
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=CAMe9rOpAgwgk8o2gyHYsd8rh7oCzS5J9Lv8-dU52b7S3krd5qA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=matz@suse.de \
/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).